A real report, of this site

Check result

• The page says when it was written or revised

  TRUST.DATE.DECLARED

  WarningLowObservedConfidence 95%

  HeuristicOur own heuristic: undated advice cannot be judged for staleness

  no <time datetime>, article:published_time or JSON-LD date

  Why it matters

  Undated advice cannot be judged for staleness, so a reader has to assume the worst. On anything where the correct answer changes — pricing, law, an API — an undated page is treated as old whether or not it is.

  How to fix

  Emit `<time datetime>` in the byline, or `article:published_time` and `article:modified_time`, or `datePublished`/`dateModified` in JSON-LD. Drive them from the stored dates rather than typing them, or they drift.

  General guidance for this rule

  How to verify

  View source and confirm a machine-readable date is present, and that it matches the date shown to a reader.

• The meta description is unique across the site

  CONTENT.DESCRIPTION.UNIQUE

  UnavailableUnavailableConfidence 100%

  Google Search Central — write unique descriptions for each page

  this check compares pages against each other
  one page was fetched, so there was nothing to compare it with

• The title is unique across the site

  CONTENT.TITLE.UNIQUE

  UnavailableUnavailableConfidence 100%

  Google Search Central — avoid duplicate titles across pages

  this check compares pages against each other
  one page was fetched, so there was nothing to compare it with

• /llms.txt is published

  GEO.LLMS_TXT.PRESENT

  UnavailableUnavailableConfidence 100%

  Heuristicllmstxt.org — a proposed convention, adopted by no engine as a requirement

  this check compares pages against each other
  one page was fetched, so there was nothing to compare it with

• hreflang is confirmed by the other page

  I18N.HREFLANG.RECIPROCAL

  UnavailableUnavailableConfidence 100%

  Google Search Central — hreflang annotations must be confirmed by the target page

  this check compares pages against each other
  one page was fetched, so there was nothing to compare it with

• Internal links resolve

  LINK.INTERNAL.HEALTHY

  UnavailableUnavailableConfidence 100%

  HeuristicOur own heuristic: a link the site makes and then breaks wastes the crawl it earned

  this check compares pages against each other
  one page was fetched, so there was nothing to compare it with

• The page is reachable from the site

  LINK.ORPHAN.NONE

  UnavailableUnavailableConfidence 100%

  HeuristicOur own heuristic: a page nothing links to is a page the site does not vote for

  this check compares pages against each other
  one page was fetched, so there was nothing to compare it with

• Cumulative Layout Shift

  PERF.CLS

  UnavailableUnavailableConfidence 100%

  web.dev — Cumulative Layout Shift, a Core Web Vital

  this check needs a timed load on a throttled connection
  no timings were captured for this run, so it was not measured

• Interaction to Next Paint

  PERF.INP

  UnavailableUnavailableConfidence 100%

  web.dev — Interaction to Next Paint, a Core Web Vital since March 2024

  this check needs a timed load on a throttled connection
  no timings were captured for this run, so it was not measured

• Largest Contentful Paint

  PERF.LCP

  UnavailableUnavailableConfidence 100%

  web.dev — Largest Contentful Paint, a Core Web Vital

  this check needs a timed load on a throttled connection
  no timings were captured for this run, so it was not measured

• Total page weight

  PERF.WEIGHT

  UnavailableUnavailableConfidence 100%

  HeuristicOur own budget for a first visit on a throttled connection

  this check needs a timed load on a throttled connection
  no timings were captured for this run, so it was not measured

• No console errors during load

  RENDER.CONSOLE.CLEAN

  UnavailableUnavailableConfidence 100%

  HeuristicOur own heuristic: a page that throws is a page at risk

  this check compares the server response against a real browser render
  no browser was used for this run, so it was not measured

• Server response matches what a browser renders

  RENDER.PARITY.CONTENT

  UnavailableUnavailableConfidence 100%

  HeuristicOur own comparison of served HTML against the rendered DOM

  this check compares the server response against a real browser render
  no browser was used for this run, so it was not measured

• Subresources load successfully

  RENDER.REQUESTS.OK

  UnavailableUnavailableConfidence 100%

  HeuristicOur own heuristic: a failed subresource is a broken page part

  this check compares the server response against a real browser render
  no browser was used for this run, so it was not measured

• Images carry alternative text

  A11Y.IMG.ALT

  Not applicableObservedConfidence 80%

  WCAG 2.2 SC 1.1.1 — non-text content

  no <img> elements on the page

• Headings introduce answerable passages

  AI.ANSWERABLE.HEADINGS

  PassInferredConfidence 60%

  HeuristicOur own heuristic: an answer engine quotes a passage under a heading

  13 of 24 headings are followed by a passage of 80+ characters
  <h1>See what holds your site back in search and AI</h1>
  <h2>Canonical points to a URL that redirects</h2>
  <h2>A report built for decisions, not vanity scores</h2>

• Content present without JavaScript

  AI.CONTENT.SERVER_RENDERED

  PassObservedConfidence 95%

  HeuristicOur own heuristic: most answer-engine crawlers do not execute JavaScript

  8617 characters of text in the server response, before any JavaScript
  <!DOCTYPE html>SEO and GEO audit with verifiable evidence — SEO Masterize Skip to contentSEO MasterizeMethodologyEvidence standardsPricingFree checkSign inEngli

• Language declared correctly

  I18N.LANG.DECLARED

  PassObservedConfidence 95%

  BCP 47 — tags for identifying languages

  <html lang="en">

• Meta description present and reasonably sized

  ONPAGE.DESCRIPTION.PRESENT

  PassObservedConfidence 80%

  HeuristicOur own budget, measured in half-width units so it holds for CJK

  "Audit technical SEO, content, structured data, Core Web Vitals and AI-search readiness. Every finding carries the evidence it was based on, a fix, and a way to re-verify it."
  173 characters, 173 half-width units (the budget is 70–200)

• A stable entity is declared

  AI.ENTITY.DECLARED

  PassObservedConfidence 95%

  HeuristicOur own heuristic: a named entity with a stable @id is quotable

  Organization @id=https://seomasterize.com/#organization
  WebSite @id=https://seomasterize.com/#website

• Answer engines are allowed to read the site

  GEO.AI_CRAWLERS.ALLOWED

  PassObservedConfidence 100%

  RFC 9309 §2.2.1 — the most specific user-agent group applies alone

  GPTBot: Allow: /  (group "*")
  OAI-SearchBot: Allow: /  (group "*")
  ClaudeBot: Allow: /  (group "*")
  PerplexityBot: Allow: /  (group "*")
  Google-Extended: Allow: /  (group "*")
  CCBot: Allow: /  (group "*")

• Redirect chain length

  HTTP.REDIRECT.CHAIN

  PassObservedConfidence 100%

  HeuristicOur own threshold: one hop is normal, two is latency on every request

  https://seomasterize.com/ → 200
  answered directly, with no redirect

• Page responds successfully

  HTTP.STATUS.OK

  PassObservedConfidence 100%

  RFC 9110 §15 — HTTP Semantics, status codes

  https://seomasterize.com/ → 200

• hreflang set is complete and self-referential

  I18N.HREFLANG.DECLARED

  PassObservedConfidence 95%

  Google Search Central — localized versions; RFC 5646 (BCP 47) tag syntax

  hreflang="en" → https://seomasterize.com/
  hreflang="es" → https://seomasterize.com/es
  hreflang="pt-BR" → https://seomasterize.com/pt-BR
  hreflang="x-default" → https://seomasterize.com/

• Canonical URL declared and self-referential

  INDEX.CANONICAL.PRESENT

  PassObservedConfidence 80%

  Google Search Central — canonicalization and rel=canonical

  <link rel="canonical" href="https://seomasterize.com/">
  resolves to  https://seomasterize.com/
  page URL     https://seomasterize.com/

• Page allows indexing

  INDEX.ROBOTS.INDEXABLE

  PassObservedConfidence 95%

  Google Search Central — robots meta tag and X-Robots-Tag

  <meta name="robots" content="index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1">
  max-image-preview:large, max-snippet:-1, max-video-preview:-1 controls how a result is PREVIEWED, not whether the page is indexed
  the page stays indexable

• Sitemap declared in robots.txt

  INDEX.SITEMAP.DECLARED

  PassObservedConfidence 100%

  Heuristicsitemaps.org protocol §4.1 — the Sitemap directive in robots.txt

  Sitemap: https://seomasterize.com/sitemap.xml

• Viewport configured for real devices

  MOBILE.VIEWPORT.PRESENT

  PassObservedConfidence 95%

  WCAG 2.2 SC 1.4.4 and the CSS Device Adaptation viewport meta

  <meta name="viewport" content="width=device-width, initial-scale=1">

• Exactly one primary heading

  ONPAGE.H1.EXACTLY_ONE

  PassObservedConfidence 80%

  HeuristicOur own heuristic: one document, one primary heading

  <h1>See what holds your site back in search and AI</h1>

• Title present and reasonably sized

  ONPAGE.TITLE.PRESENT

  PassObservedConfidence 80%

  HTML Standard §4.2.2 — the title element

  <title>SEO and GEO audit with verifiable evidence — SEO Masterize</title>
  58 characters, 58 half-width units (the budget is 15–70)

• Structured data parses and declares a type

  SD.JSONLD.VALID

  PassObservedConfidence 95%

  schema.org and Google Search Central — structured data guidelines

  1 block(s)
  types: Organization, WebSite, FAQPage

• Served over HTTPS

  SEC.HTTPS.SERVED

  PassObservedConfidence 100%

  Google Search Central — HTTPS as a ranking signal

  https://seomasterize.com/

• The page says who wrote it

  TRUST.AUTHOR.DECLARED

  PassObservedConfidence 95%

  HeuristicOur own heuristic: a claim nobody signed is a claim nobody owns

  author: SEO Masterize

• A reader can find a way to reach you

  TRUST.CONTACT.REACHABLE

  PassInferredConfidence 80%

  HeuristicOur own heuristic: a site with no way to reach anyone is harder to trust

  /contact