CrawlGap 39 — Example Domain

Crawler access96

Readability without JavaScript78

Machine-readable structure27

Answer-readiness11

Technical foundations70

Findings

high Readability without JavaScript

Very little text on the page for either humans or machines

Evidence: 17 words of body text after rendering.
Why it costs citations: Assistants need extractable prose to quote. A page that is mostly imagery and headings gives them nothing to lift, so a competitor with written detail wins the mention.
Fix: Add 400+ words that answer the questions buyers actually ask: what you do, who for, where, what it costs, how to start.

high Machine-readable structure

No Organization / LocalBusiness structured data

Evidence: No JSON-LD found in the raw HTML.
Why it costs citations: This is the block that tells an assistant the entity name, what kind of business it is, where it operates and how to contact it. Without it the assistant has to guess from prose, and it frequently guesses a competitor with clearer markup.
Fix: Add a server-rendered JSON-LD Organization (or LocalBusiness for a physical location) with name, url, logo, description, telephone, address, sameAs links to your profiles, and areaServed.

high Answer-readiness

No headings are phrased as questions people actually ask

Evidence: 1 headings, none in question form.
Why it costs citations: Assistants retrieve by matching a user question to a passage. A heading that restates the question, followed immediately by a direct answer, is the highest-probability shape for being lifted and cited.
Fix: Convert or add headings like "How much does X cost in <city>?", "How long does X take?", "Do you offer X on weekends?" — each followed by a 2–3 sentence direct answer.

high Answer-readiness

No machine-readable way to contact the business

Evidence: tel: links 0, mailto/emails 0, WhatsApp links 0. Phone-shaped strings in text: 0.
Why it costs citations: When an assistant recommends a business, the next thing it tries to supply is how to reach it. A phone number that exists only inside an image or a JS widget cannot be handed to the customer, so the recommendation goes to whoever published a plain tel: link.
Fix: Add <a href="tel:+91…">, a mailto: link, and a wa.me click-to-chat link in the server-rendered HTML, plus telephone/email in your Organization schema.

medium Machine-readable structure

No FAQPage structured data

Evidence: No FAQPage / Question markup in the raw HTML.
Why it costs citations: Question-and-answer markup is the format answer engines lift most directly, because each answer is already a self-contained, attributable unit.
Fix: Publish 6–10 real customer questions with short direct answers, marked up as FAQPage, rendered server-side.

medium Answer-readiness

No meta description

Evidence: Missing on the homepage.
Why it costs citations: The description is often reused verbatim as the one-line summary of the business in AI and search results. Leaving it blank means something else gets chosen for you.
Fix: Write a 140–160 character description that names the service, the audience and the location.

medium Answer-readiness

No lists or tables in the raw HTML

Evidence: 2 paragraphs, 0 lists, 0 tables.
Why it costs citations: Lists and tables are the easiest structures for an assistant to extract cleanly and reproduce — pricing tiers, service areas, timings, inclusions.
Fix: Convert dense prose about pricing, coverage and process into <ul> and <table> markup.

medium Technical foundations

No XML sitemap found

Evidence: Checked /sitemap.xml.
Why it costs citations: A sitemap is how a crawler finds pages that are not well linked — exactly the pages that JavaScript navigation already hides.
Fix: Generate sitemap.xml with every indexable URL and reference it from robots.txt with "Sitemap: https://…/sitemap.xml".

low Crawler access

No robots.txt found

Evidence: GET /robots.txt returned 404.
Why it costs citations: Nothing is blocked, so this is not urgent — but you also have no place to declare a sitemap or set per-bot policy, and some crawlers back off on repeated 5xx.
Fix: Publish a robots.txt that explicitly allows the retrieval bots you want and lists your Sitemap: URL.

low Machine-readable structure

No BreadcrumbList structured data

Evidence: Not found in raw HTML.
Why it costs citations: Breadcrumbs help a retrieval system understand where a page sits in the site hierarchy, which improves how it is described when cited.
Fix: Add BreadcrumbList JSON-LD on inner pages.

low Machine-readable structure

Open Graph tags are incomplete

Evidence: og:title missing, og:description missing, og:image missing.
Why it costs citations: Open Graph controls how the link looks when shared into WhatsApp, Slack and social feeds — the places prospects actually pass a link around.
Fix: Add og:title, og:description and a 1200×630 og:image.

low Answer-readiness

Title is 14 characters

Evidence: "Example Domain"
Why it costs citations: A very short title omits the service and location terms people ask about.
Fix: Aim for 45–60 characters, leading with what you do and where.

low Answer-readiness

No machine-readable dates on the page

Evidence: No <time datetime> elements and no dated schema.
Why it costs citations: Assistants prefer sources they can date, and prefer recent ones when a question is time-sensitive.
Fix: Add <time datetime="YYYY-MM-DD"> for published/updated, and datePublished/dateModified in schema.

low Technical foundations

No HSTS header

Evidence: Strict-Transport-Security not set.
Why it costs citations: Without HSTS the first request each visit can still be attempted over HTTP.
Fix: Send Strict-Transport-Security: max-age=31536000; includeSubDomains once you are confident HTTPS works everywhere.

low Technical foundations

No canonical URL declared

Evidence: Missing <link rel="canonical">.
Why it costs citations: Without a canonical, the same content reachable at several URLs (www/non-www, trailing slash, tracking parameters) can be treated as duplicates and split its authority.
Fix: Add a self-referential absolute canonical tag to every page.

low Technical foundations

No character encoding declared

Evidence: Missing <meta charset>.
Why it costs citations: Encoding guesses corrupt non-ASCII text — names, currency symbols, Indic scripts.
Fix: Add <meta charset="utf-8"> as the first element in <head>.

pass Readability without JavaScript

Content is present in the raw HTML

Evidence: Raw HTML carries 17 of 17 rendered words (100%).
Why it costs citations: AI crawlers receive substantially the same content a human sees. This is the single biggest thing most sites get wrong, and it is right here.

What an AI crawler reads

Example DomainThis domain is for use in documentation examples without needing permission. Avoid use in operations.Learn more

What a human sees after JavaScript

Example DomainThis domain is for use in documentation examples without needing permission. Avoid use in operations.Learn more

robots.txt

<!doctype html><html lang="en"><head><title>Example Domain</title><link rel="icon" href="data:,"><meta name="viewport" content="width=device-width, initial-scale=1"><style>body{background:#eee;width:60vw;margin:15vh auto;font-family:system-ui,sans-serif}h1{font-size:1.5em}div{opacity:0.8}a:link,a:visited{color:#348}</style></head><body><div><h1>Example Domain</h1><p>This domain is for use in documentation examples without needing permission. Avoid use in operations.</p><p><a href="https://iana.org/domains/example">Learn more</a></p></div></body></html>