Duly: Life, organized the way you wish.

Description is 54 characters, under this audit's 70-character review point (a heuristic, not a Google minimum).

The title and description are the text someone reads in a search result before deciding whether to click. It is there, but weaker than this check expects.

Add useful context if the summary omits the page purpose. Do not pad it or force keywords to reach a count.

Title found: "Duly: Life, organized the way you wish."

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Title is 39 characters, inside this audit's 15–60 review range.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Title "Duly: Life, organized the way you wish." says more than the site name.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

Meta description found: "Just ramble. Duly handles it all. For iPhone and iPad."

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

All 2 indexable sampled pages have distinct titles.

The title and description are the text someone reads in a search result before deciding whether to click. The inspected source provides this signal.

Nothing to do here.

No sitemap found (checked https://www.useduly.app/sitemap.xml → 404).

These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.

Publish a sitemap.xml and submit it in Google Search Console. Next.js: export from app/sitemap.ts — it's ~10 lines.

The page was served from www.useduly.app but its canonical names useduly.app.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.

Pick one host, 301-redirect the other to it, and use it in the canonical, sitemap and internal links. Right now www.useduly.app answers without redirecting.

Mixed hostnames in use: www.useduly.app, useduly.app.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. It is there, but weaker than this check expects.

Pick one (www or apex), 301 the other to it, and use it consistently in canonical/og:url/sitemap.

No sitemap was found, so there are no submitted URLs to compare against.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

The sitemap check covers the missing file. Once one exists, this check confirms the URLs it lists are indexable.

robots.txt is absent. A missing policy permits crawling by default.

These rules decide whether the page can be indexed at all. One wrong directive hides good work. This check does not apply to the features observed in this sample.

Optional: publish a robots policy to advertise a sitemap or restrict selected paths.

No sitemap was reachable, so its contents cannot be validated.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Publish /sitemap.xml with your canonical URLs. This check then validates the XML and the URLs it lists.

The audited page has about 215 words of main content, on the thin side.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. It is there, but weaker than this check expects.

Add useful text where a visitor would expect it: what this is, who it is for, and answers to the questions a first-time visitor asks. Word count itself is not a ranking factor.

Flesch reading ease ≈ 80.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

60+ reads easily for most visitors. This is a heuristic, not a rule — technical audiences tolerate denser text.

No recognized empty JavaScript application shell on 5 sampled page(s). The entered page exposes 215 publisher word(s).

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

Text-to-HTML ratio is 15.1%.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

No placeholder text detected on crawled pages.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

No starter-template artifacts detected.

This is the substance of the page. Placeholders and repeated copy make it read as unfinished. The inspected source provides this signal.

Nothing to do here.

No og:site_name tag.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add it. Share cards use it to label the publisher; consistent naming also gives this audit a measurable entity signal. It does not measure or guarantee citations, rankings, or traffic.

og:title: "Duly: Life, organized the way you wish."

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:description: "Just ramble. Duly handles it all."

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:image is set: "https://useduly.app/og/beta.jpg"

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:image returns 200 (image/jpeg).

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

Dimensions declared: 1200×628.

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

og:url and og:type ("website") are set.

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

twitter:card is "summary_large_image".

This is what your link looks like when someone drops it into a chat or a feed. The inspected source provides this signal.

Nothing to do here.

No JSON-LD structured data on the homepage.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.

Add Organization and WebSite schema. They state who publishes the site and what it is called, which is what rich results and answer engines read first.

No Organization, WebSite or Person schema found.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. It is there, but weaker than this check expects.

Add an identity node so search engines and AI assistants can attribute your content to a real entity.

No JSON-LD blocks were found, so there is no syntax to validate.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.

Add a <script type="application/ld+json"> block describing the page — Organization or WebSite is the usual starting point.

None of the 4 crawled inner pages declare BreadcrumbList schema.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add BreadcrumbList to inner pages — Google shows breadcrumbs in results and it clarifies site structure.

• https://www.useduly.app/privacy
• https://www.useduly.app/
• https://www.useduly.app/tr
• https://www.useduly.app/support

No content-specific schema (Article, Product, FAQPage…) detected.

Structured data tells machines who published the page and what it describes. Broken markup is ignored outright. This check does not apply to the features observed in this sample.

If you publish articles, products or FAQs, add the matching schema type — that's what makes rich results (stars, FAQs, prices) possible.

H1 found: "Life. Organized the way you wish."

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

Exactly one H1 on the homepage.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

Heading hierarchy is sequential across 9 headings.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

H1 reads "Life. Organized the way you wish.".

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

9 headings, averaging 3.2 words — descriptive.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

7 H2 section(s) structure the page.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

All inspected element IDs are unique within their documents.

Headings are the outline every parser and screen reader follows to find the answer. The inspected source provides this signal.

Nothing to do here.

1 of 1 raster images are served only as PNG or JPEG: ipad.png.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. It is there, but weaker than this check expects.

Serve WebP or AVIF versions, which are usually 25–50% smaller at the same quality. Use <picture> with a WebP/AVIF <source> and the original as fallback, or an image CDN or framework image component that converts automatically.

Only 2 visible image(s) on the page, too few for lazy loading to change the initial load.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. This check does not apply to the features observed in this sample.

Nothing to change here. Once the page carries several images, add loading="lazy" to the ones below the fold.

All 2 visible images declare alt attributes (including empty alt for decorative images). Whether each description fits its image needs a human look.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

All 2 visible images declare dimensions or are sized by their container.

Alt text is what a screen reader announces, and what image search and AI systems read in place of the picture. The inspected source provides this signal.

Nothing to do here.

All 4 sampled internal links return < 400.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

9 of 9 links have descriptive text or labels.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

No placeholder links on the audited page.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

All target="_blank" links carry rel="noopener".

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

Homepage links to 3 distinct internal pages.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

3 same-page fragment link(s) have source targets.

Links are how visitors and crawlers reach the rest of the site. A broken one is a dead end. The inspected source provides this signal.

Nothing to do here.

Only 2 image(s) on the page, too few for responsive image markup to change what phones download.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Nothing to change here. When the page carries several images, give them srcset and sizes so phones fetch smaller files.

No sub-12px inline font sizes detected; stylesheet rules and rendered sizes were not measured.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Check computed font sizes in a browser across mobile widths.

No ARIA ID references found in the sampled HTML.

Google indexes the phone rendering, so that is the version being graded. This check does not apply to the features observed in this sample.

Verify rendered accessibility separately.

Viewport configured: "width=device-width, initial-scale=1, viewport-fit=cover".

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

The viewport lets users zoom.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

42 source controls have detectable names. Browser accessibility and CSS visibility were not tested.

Google indexes the phone rendering, so that is the version being graded. The inspected source provides this signal.

Nothing to do here.

Language declared: lang="en".

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

3 syntactically valid hreflang tags including x-default. Reciprocal links and target content were not verified.

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

Declared language (en) matches detected content language.

The declared language tells browsers and assistive tech how to read the page and who it is for. The inspected source provides this signal.

Nothing to do here.

No apple-touch-icon link.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add a 180×180 apple-touch-icon so iOS home-screen bookmarks show your logo instead of a screenshot.

No web manifest linked.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Optional, but a manifest.json enables install prompts and better mobile integration.

No theme-color meta tag.

This observation could not be established from the available evidence. Resolve the collection limit or inspect the relevant source before deciding whether a change is needed.

Add <meta name="theme-color"> to tint the mobile browser UI to your brand color. Small touch, feels polished.

Favicon declared via <link rel="icon"> (/favicon-32.png).

These icons are what appear in browser tabs, bookmarks and search results. The inspected source provides this signal.

Nothing to do here.