Test Paid Audit

Can AI engines actually read your site?

• Fix

  Content rendered server-side

  Your important content is in the initial HTML response, not rendered by JavaScript afterwards. Most AI crawlers don't execute JS, so client-rendered content is invisible to them.

  Homepage HTML contains only ~21 words of visible text (142 characters). Content is almost certainly JS-rendered.

  What to do: Most AI crawlers don't execute JavaScript. Switch to server-side rendering (Next.js, Nuxt, etc.) or pre-render your pages.

• Fix

  Sitemap.xml present and submitted

  A complete sitemap.xml exists, lists all important pages, is referenced in robots.txt, and is submitted to Google Search Console and Bing Webmaster Tools.

  No sitemap found at /sitemap.xml and no Sitemap: directive in robots.txt.

  What to do: Generate a sitemap.xml listing all important pages and submit it to Google Search Console and Bing Webmaster Tools.

• Improve

  Canonical tags set correctly

  Every page declares a canonical URL, with no conflicting or self-referential errors. Critical for e-commerce with faceted navigation.

  No <link rel='canonical'> tag found on the homepage.

  What to do: Add a canonical tag pointing to the preferred URL of each page. Critical when you have URL parameters or faceted navigation.

• Improve

  robots.txt allows AI crawlers

  Your robots.txt explicitly allows GPTBot, ClaudeBot, PerplexityBot, CCBot, and Google-Extended. Blocking any of them — even by accident — makes you invisible to that platform.

  No robots.txt found at /robots.txt. AI crawlers default to allowed without one, but an explicit allow file is preferred.

  What to do: Publish a robots.txt at the site root. List user agents like GPTBot, ClaudeBot, PerplexityBot with 'Allow: /' to make your stance unambiguous.

• Manual review

  Critical content is not PDF-only

  Case studies, product specs, and white papers exist as crawlable HTML pages, not just downloadable PDFs. AI cites HTML pages roughly 10x more often than PDFs.

  Multi-page crawl needed to detect PDF-only content.

  What to do: Ensure case studies, product specs, and white papers exist as crawlable HTML, not only PDFs. AI cites HTML pages 10x more than PDFs.

• Good

  Cloudflare WAF doesn't block AI bots

  Cloudflare's 'Block AI Scrapers and Crawlers' setting and default Bot Fight Mode can silently block AI crawlers. Verify the rules don't apply to GPTBot, ClaudeBot, etc.

  AI crawlers can reach your site. GPTBot received HTTP 200; ClaudeBot received HTTP 200.

• Good

  Full HTTPS, no mixed content

  Every page loads over HTTPS with a valid certificate, and no internal links or assets fall back to HTTP.

  Site loads over HTTPS with no detected mixed content.

Can AI agents not just read, but act on your site?

• Fix

  Agent Skills index published

  A /.well-known/agent-skills/index.json file (Agent Skills Discovery RFC v0.2.0) lists callable skills agents can invoke. Each skill has a name, type, description, URL and sha256 digest. Cloudflare-led standard, increasingly required.

  No Agent Skills index found at /.well-known/agent-skills/index.json.

  What to do: Publish an Agent Skills index (Cloudflare's RFC v0.2.0) listing callable skills agents can invoke. Each skill needs a name, type, description, URL and sha256 digest.

• Fix

  Content Signals declared in robots.txt

  Use the Content-Signal directive (format: search=yes, ai-input=yes, ai-train=no) to declare how AI may use your content. Distinct from Allow/Disallow — silence is increasingly interpreted as restrictive.

  No robots.txt found, so no Content-Signal declarations can be made.

  What to do: Publish a robots.txt and add a Content-Signal directive declaring how AI may use your content.

• Fix

  MCP Server Card available

  A /.well-known/mcp.json file declares which actions agents can take on your site (book, submit, query). Emerging standard backed by Anthropic and adopted by Claude Desktop and ChatGPT. Fewer than 100 sites worldwide have one.

  No MCP server card found at /.well-known/mcp.json.

  What to do: Publish an MCP server card declaring actions agents can take on your site. Emerging standard backed by Anthropic. Fewer than 100 sites worldwide have one — strong differentiator.

• Fix

  Markdown content negotiation supported

  When an AI agent sends 'Accept: text/markdown', your server responds with a clean Markdown version of the page. Saves tokens for the agent — agents are more likely to cite low-token sources. Less than 4% of sites do this.

  Asked for markdown but got Content-Type: text/html.

  What to do: Set up your server to return text/markdown when requested. Either pre-generate .md twins of your key pages or run a lightweight HTML→Markdown conversion middleware.

• Fix

  RFC 8288 Link headers for discovery

  HTTP Link response headers point agents to your well-known resources (mcp-server, api-catalog, agent-skills, sitemap, llms.txt) without parsing HTML. Agents using HEAD requests or Markdown negotiation only see headers, not <link> tags.

  No HTTP Link headers found on the homepage.

  What to do: Add a Link response header pointing to your well-known resources (llms.txt, sitemap.xml, mcp.json, etc). Agents using HEAD requests or markdown negotiation never see <link> tags in HTML — only headers.

• Fix

  llms.txt file published

  An llms.txt at the site root tells AI agents what your site is about and points to the most authoritative pages. Less than 1% of sites have one — a free differentiator.

  No llms.txt found at /llms.txt.

  What to do: Publish an llms.txt at the site root summarising what the site is about and pointing AI agents to your most authoritative pages. See llmstxt.org for the format. Fewer than 1% of sites have one.

• Manual review

  Forms readable and submittable by agents

  Forms use semantic HTML (proper labels, autocomplete attributes, aria-required), don't rely on heavy JS for validation, and accept standard form-encoded POST. An agent can fill them without computer-vision tricks.

  No <form> found on the homepage.

  What to do: If you have forms on other pages (contact, signup, search), ensure they use semantic HTML — proper labels, autocomplete attributes, and standard form-encoded POST. Agents struggle with custom JS form components.

• Manual review

  OAuth Protected Resource Metadata

  If you offer protected APIs, publish /.well-known/oauth-protected-resource (RFC 9728) declaring the authorization servers that can issue tokens for it and the supported scopes. Lets agents discover how to authenticate before attempting access.

  Manual review required — only relevant if you offer protected APIs.

  What to do: If you offer protected APIs, publish /.well-known/oauth-protected-resource (RFC 9728) declaring authorization servers and supported scopes.

• Manual review

  OAuth/OIDC discovery metadata

  If your site has authenticated areas (account, dashboard), expose /.well-known/openid-configuration or /.well-known/oauth-authorization-server so agents can authenticate programmatically. Required for any future agent-driven workflow that touches user data.

  Manual review required — only relevant if your site has authenticated areas.

  What to do: If you have user accounts or a dashboard, expose /.well-known/openid-configuration or /.well-known/oauth-authorization-server so agents can authenticate programmatically.

• Manual review

  Public API catalog (RFC 9727)

  /.well-known/api-catalog (application/linkset+json) lists your public APIs with service-desc (OpenAPI), service-doc and status endpoints. Agents discover and integrate without scraping.

  No API catalog found at /.well-known/api-catalog. Only relevant if you offer public APIs.

  What to do: If you offer public APIs, publish /.well-known/api-catalog (RFC 9727) listing them with service-desc (OpenAPI), service-doc and status endpoints.

• Manual review

  WebMCP browser-side tool registration

  Call navigator.modelContext.provideContext() with tool definitions so AI-equipped browsers (Chrome with Gemini, Edge with Copilot) can invoke your site's actions client-side. Feature-detected; harmless on browsers without WebMCP.

  Manual review required — checks for navigator.modelContext.provideContext() calls in your JS.

  What to do: Call navigator.modelContext.provideContext() with tool definitions so AI-equipped browsers (Chrome with Gemini, Edge with Copilot) can invoke your site's actions client-side. Feature-detected — safe to add.

How clearly machines can understand who you are.

• Fix

  FAQ schema on key pages

  FAQ schema markup on pages that genuinely answer customer questions. Don't fake it — Google penalises FAQ stuffing, and AI engines verify against page content.

  No FAQPage schema found on the homepage.

  What to do: If you answer common customer questions anywhere on your site, mark them up with FAQPage JSON-LD. Don't fake it — Google penalises FAQ stuffing.

• Fix

  Organization schema

  JSON-LD Organization schema on the homepage with name, logo, URL, sameAs links to social profiles, address, and contact info. This is the single most-cited structured data block by AI.

  No JSON-LD Organization schema found on the homepage.

  What to do: Add a JSON-LD Organization block on the homepage with name, logo, URL, sameAs (social links), address, and contact info. This is the most-cited structured data block by AI.

• Fix

  sameAs linking to social and directories

  Organization schema includes sameAs URLs to your LinkedIn, Wikipedia, Crunchbase, industry directories — all the entities AI uses to build a trustworthy picture of you.

  No Organization or LocalBusiness schema found, so sameAs cannot be evaluated.

  What to do: Once you have an Organization schema, add a sameAs array linking to your LinkedIn, X, Crunchbase, Wikipedia, and industry directory profiles.

• Improve

  LocalBusiness schema

  LocalBusiness (or specific subtype like Restaurant, Store) schema with address, hours, geo coordinates, price range, and aggregated review rating.

  No LocalBusiness schema found on the homepage.

  What to do: If you have a physical location, add LocalBusiness JSON-LD with name, address, telephone, openingHoursSpecification, and a geo.latitude / geo.longitude. Restaurants and shops are the main beneficiaries.

• Manual review

  Article schema on content pages

  Blog posts and case studies use Article schema with author, datePublished, and dateModified. AI weighs freshness signals.

  No Article / BlogPosting schema on the homepage. Typically lives on individual blog posts.

  What to do: If you publish blog posts or articles, mark each one with Article JSON-LD: headline, author, datePublished, image. Boosts AI citation in 'best X' style queries.

• Manual review

  BreadcrumbList schema

  BreadcrumbList schema on category and product pages helps AI understand your site hierarchy.

  No BreadcrumbList schema on the homepage. This is typically added on inner pages (product, category) rather than the home.

  What to do: Add BreadcrumbList JSON-LD on inner pages so AI can place each page in your site hierarchy.

• Manual review

  Person schema for leadership

  Founders and key staff have Person schema with role, credentials, and sameAs links to LinkedIn. Helps AI characterize who runs the business.

  No Person schema for leadership on the homepage.

  What to do: Founders and key staff should have Person schema with role, credentials, and sameAs links to LinkedIn. Typically on the About or Team pages.

• Manual review

  Product schema with reviews

  Product schema on every product page with brand, GTIN/SKU, price, availability, and aggregated reviews. Drives both rich results in Google and citations in shopping AI agents.

  This criterion applies to e-commerce businesses. Your declared business type is 'other', so it's not a priority for you.

  What to do: Skip this one unless you also sell products online. If you do, ensure each product page has Product JSON-LD with brand, GTIN/SKU, price, availability, and aggregateRating.

• Manual review

  Service schema per core offering

  Each main service has its own page with Service schema, describing what it is, who it's for, and areas served.

  No Service schema on the homepage. Typically lives on individual service pages.

  What to do: Each main service should have its own page with Service JSON-LD describing what it is, who it's for, and areas served.

How easy it is for AI to quote you.

• Fix

  Long-form About page

  Substantive About page (1,000+ words) covering history, philosophy, team, and concrete differentiators. The single page AI cites most when answering 'who is X' queries.

  Homepage has only ~21 words — likely too thin for AI to characterize the business.

  What to do: Build a long-form About page (1,000+ words). The single page AI cites most when answering 'who is X' queries.

• Fix

  Specific numbers in your claims

  Concrete metrics ('320 projects since 2008', 'OEE improved 18%') rather than vague adjectives ('large portfolio', 'great results'). AI rewards specificity with citations.

  Homepage uses fewer than 1 specific numeric claims. Mostly vague language.

  What to do: Replace vague adjectives ('large portfolio', 'great results') with concrete metrics. AI cites businesses with specific, verifiable claims.

• Improve

  FAQ section answering buyer questions

  An FAQ section on the homepage or a dedicated FAQ page that answers common buyer questions in clear, quotable language.

  No FAQ section detected on the homepage.

  What to do: Add an FAQ section answering 5-10 common buyer questions in clear, quotable language. AI engines quote FAQ blocks heavily.

• Improve

  Menu / pricing publicly visible

  Restaurant menus and service prices are on the website as HTML text — not behind PDF, image, or login. AI cannot quote what it cannot read.

  No pricing or menu link detected on the homepage.

  What to do: Mainly for restaurants and local shops — menus and prices should be visible HTML, not PDF or login-walled. AI cannot quote what it cannot read.

• Manual review

  Case studies in crawlable HTML

  Each case study is a public HTML page with client name (where permitted), problem, solution, technologies used, and measurable outcomes. Not just a PDF download.

  Case studies presence and quality need a multi-page crawl. Upgrade to Standard or Expert for automated analysis.

  What to do: Each case study should be a public HTML page with client, problem, solution, technologies, and measurable outcomes.

• Manual review

  Comparison and 'vs' pages

  Honest comparison pages versus competitors or alternatives. AI surfaces these for high-intent comparison queries.

  Comparison/'vs' page presence needs a multi-page crawl. Upgrade to Standard or Expert for automated analysis.

  What to do: Build honest comparison pages versus competitors. AI surfaces these for high-intent comparison queries.

• Manual review

  Detailed product specifications

  Product pages include full specs, dimensions, materials, compatibility, and clear use-case descriptions. AI shopping agents filter by these attributes.

  Detailed product specs are primarily relevant for e-commerce businesses (your type: 'other').

  What to do: Product pages should include full specs, dimensions, materials, compatibility, and use-case descriptions.

• Manual review

  Industry-vertical pages

  Dedicated pages for each vertical you serve, with the language, use cases, and outcomes specific to that industry. AI excels at recommending vertical-specific service providers.

  Industry vertical pages are primarily relevant for B2B businesses (your type: 'other').

  What to do: Build dedicated pages for each vertical you serve, with industry-specific language and use cases.

• Manual review

  Technology / platform pages

  Explicit pages naming every major technology you work with (e.g., Siemens, Rockwell, Shopify, Salesforce). AI looks for exact-match technology terms when matching buyer intent.

  Technology/platform pages are primarily relevant for B2B software businesses (your type: 'other').

  What to do: Build explicit pages naming every major technology you work with (Siemens, Salesforce, etc).

Whether AI can describe who you are in two sentences.

• Improve

  Clear two-sentence positioning

  Your home page hero, About page, and meta description all say what you do and who for in two sentences a stranger could repeat. AI cannot recommend what it cannot summarize.

  Positioning is unclear: no <meta name=description>.

  What to do: Write a concise H1 and a 80-160 character meta description that say what you do and who for in two sentences a stranger could repeat.

• Improve

  Consistent business name everywhere

  Same exact business name across website, Google Business, LinkedIn, social, directories, and press. Inconsistencies fragment the entity in AI's understanding.

  Business name 'Test Paid Audit' (as submitted) does not appear verbatim on the homepage.

  What to do: Use the same exact business name everywhere — website, Google Business, LinkedIn, directories. Inconsistencies fragment the entity in AI's understanding.

• Improve

  Wikipedia mention or page

  A Wikipedia page (where notability allows) or mentions in relevant Wikipedia articles. Wikipedia is one of the most heavily weighted citation sources by AI engines.

  Your business name appears in Wikipedia search results but no dedicated article clearly matches it (closest: “Computer-aided audit tools”). This may be passing mentions or a similarly-named entity.

  What to do: Where notability allows, work toward a Wikipedia article — or get cited in relevant existing articles. Wikipedia is one of the most heavily weighted sources AI engines draw on. This is a long-game move: it compounds once it's there.

• Manual review

  Consistent NAP (name, address, phone)

  NAP information matches exactly across every directory and platform. A single typo in your address can cost local visibility.

  NAP consistency requires cross-referencing your site with directories.

  What to do: Verify your name, address, and phone number match exactly on website, Google Business, LinkedIn, social profiles, and directories.

What outside sources back you up.

• Manual review

  Active LinkedIn company page

  Complete LinkedIn company page with regular posting (1-2 per week minimum) and a meaningful follower count. Heavy AI citation source for B2B.

  Off-site signal — requires manual research or external API.

  What to do: Maintain a complete LinkedIn company page with 1-2 posts per week and meaningful follower count.

• Manual review

  Founder LinkedIn presence

  Founders publish technical or strategic posts with some regularity. Personal brand of leadership amplifies company visibility in B2B contexts.

  Off-site signal — requires manual research or external API.

  What to do: Founders should publish technical or strategic posts regularly.

• Manual review

  Industry directory listings

  Listings in directories specific to your sector, with complete profiles and consistent information.

  Off-site signal — requires manual research or external API.

  What to do: List in directories specific to your sector with complete, consistent profiles.

• Manual review

  Original research or data publication

  Published reports based on data only you have (industry surveys, methodology papers, internal benchmarks). The highest-leverage long-game move — gets cited for years.

  Off-site signal — requires manual research or external API.

  What to do: Publish reports based on data only you have. Highest-leverage long-game move — gets cited for years.

• Manual review

  Press and media coverage

  Mentions in publications AI trusts (sector-specific or regional press). Even a single feature in a respected outlet moves the needle.

  Off-site signal — requires manual research or external API.

  What to do: Get mentions in sector or regional press. Even a single feature in a respected outlet moves the needle.

• Manual review

  Speaking engagements and panel slots

  Conference talks, panels, and podcast appearances. Each one produces durable content that AI later cites.

  Off-site signal — requires manual research or external API.

  What to do: Speak at conferences, on panels, podcast appearances. Each produces durable content AI later cites.

• Manual review

  Third-party reviews on trusted sites

  Reviews on Google, TripAdvisor, Trustpilot, G2, Capterra, or sector-specific directories. AI weighs aggregated review presence as a credibility signal.

  Off-site signal — requires manual research or external API.

  What to do: Build review presence on Google, TripAdvisor, Trustpilot, G2, Capterra, or sector-specific directories.

Visibility for queries with a place attached.

• Manual review

  City and neighborhood named on the site

  Your city and neighborhood appear naturally in the homepage copy, About, and footer. AI cross-references these against the place names in user queries.

  No city-level location was provided for this audit, so we could not check the homepage automatically.

  What to do: Make sure your city and neighborhood appear naturally in homepage copy, About, and footer. AI cross-references these against place names in user queries.

• Manual review

  Google Business & maps presence

  Your presence across Google Business Profile, Google reviews, and the wider maps ecosystem (Apple Maps, Bing Places).

  • Manual review Google Business Profile fully filled

    Local signal — requires Google Business Profile API or manual verification.

    What to do: Fill every field of your Google Business Profile — categories, services, attributes, photos, hours, posts.

  • Manual review Recent photos on Google Business

    Local signal — requires Google Business Profile API or manual verification.

    What to do: Upload fresh photos monthly: interior, products, team, events. Drives ranking and click-through.

  • Manual review Google reviews — volume and recency

    Local signal — requires Google Business Profile API or manual verification.

    What to do: Build a steady inflow of reviews with proprietor responses on most.

  • Manual review Apple Maps and Bing Places presence

    Local signal — requires Google Business Profile API or manual verification.

    What to do: List on Apple Maps and Bing Places, both increasingly cited by AI.

Speed and stability metrics that gate ranking.

• Manual review

  Modern image formats and compression

  Images served as WebP or AVIF, properly sized for the device, with lazy loading on below-the-fold content.

  This metric wasn't available from the speed test for this site — verify it manually with PageSpeed Insights.

  What to do: Serve images as WebP or AVIF, sized for the device, with lazy-loading on anything below the fold.

• Manual review

  No render-blocking resources

  Critical CSS is inlined. Non-critical CSS and JS are deferred or async-loaded. Especially important for ad-heavy or analytics-heavy sites.

  This metric wasn't available from the speed test for this site — verify it manually with PageSpeed Insights.

  What to do: Inline the critical CSS and defer or async-load the rest of your CSS and JavaScript.

• Good

  Cumulative Layout Shift (CLS) under 0.1

  Your layout doesn't jump around as it loads. Frequent CLS issues come from images without dimensions and late-loading ads.

  Cumulative Layout Shift: 0.000 (real-user data, p75). Google's 'good' threshold is 0.1.

• Good

  Interaction to Next Paint (INP) under 200ms

  Your site responds instantly to clicks and taps. INP replaced FID as a Core Web Vital in 2024.

  Interaction to Next Paint: 0.08s (real-user data, p75). Google's 'good' threshold is 0.2s.

• Good

  Largest Contentful Paint (LCP) under 2.5s

  Your main content loads quickly. LCP is one of three Core Web Vitals Google uses as a ranking signal.

  Largest Contentful Paint: 0.95s (real-user data, p75). Google's 'good' threshold is 2.5s.

Does your site hold up on a phone?

• Manual review

  No intrusive mobile interstitials

  No full-screen popups or cookie banners that block content on mobile. Google demotes pages with intrusive interstitials.

  Interstitial detection needs computed rendering, deferred to Lighthouse integration.

  What to do: Avoid full-screen popups or cookie banners that block content on mobile. Google demotes pages with intrusive interstitials.

• Good

  Proper mobile viewport meta tag

  viewport meta tag is set correctly so the site adapts to phone screens. Should be standard, but is still missing on older sites.

  Viewport meta tag is properly set: width=device-width, initial-scale=1

Who links to you, and from where.

• Manual review

  Backlinks from quality domains

  Inbound links from domains with real authority — sector publications, partner companies, education or government sites. Quality matters far more than quantity.

  Backlink data — requires Ahrefs/Moz API, deferred to a later pack.

  What to do: Build inbound links from authoritative domains — sector publications, partner companies, gov/edu sites.

• Manual review

  Natural anchor text profile

  Backlinks to your site use varied, natural anchor text. Over-optimised anchor text (same keywords repeatedly) triggers spam signals.

  Backlink data — requires Ahrefs/Moz API, deferred to a later pack.

  What to do: Keep backlink anchor text varied and natural; over-optimisation triggers spam signals.

• Manual review

  No toxic or spammy backlinks

  Your backlink profile is free of paid-link networks, scraper sites, and irrelevant low-quality directories. Disavow if necessary.

  Backlink data — requires Ahrefs/Moz API, deferred to a later pack.

  What to do: Audit and disavow paid-link networks and irrelevant directories if necessary.

• Manual review

  Strong internal linking structure

  Important pages are linked from many other pages on your site, with descriptive anchor text. Helps AI understand your site hierarchy and what matters most.

  Backlink data — requires Ahrefs/Moz API, deferred to a later pack.

  What to do: Link important pages from many places on your site with descriptive anchor text.