Audit Standard / 2026.4
Rule explorer: Audit Standard 2026.4
Every check that defines technical readiness in MaxiMarket Audit Standard 2026.4, exactly as the audit applies it. Open a rule to see what it checks, why it matters, how to fix it, where its authority comes from and how much it counts.
Guides by topic: technical SEO audit rules, AI readiness, structured data and ecommerce product data.
Authority levels
- A search engine documents it as required for a specific outcome, such as Google eligibility.
- Strongest external authority
- Defined by an open standard or vocabulary: HTML, WCAG, IETF RFCs, Schema.org, Sitemaps, Open Graph.
- Recommended in official platform documentation, such as Google Search Central or an AI platform.
- Widely accepted practice with a cited source, but no official requirement.
- MaxiMarket’s own advice. Never presented as a search engine or platform requirement.
- MaxiMarket methodology
Filter
Showing 3 rules and 0 observations.
Rules
Rules pass or fail. A failed rule becomes a finding in your report; scored rules also count toward the Technical Score.
Headings and semantic structure
SEO-HEADING-001Page has a top-level headingDocumentWarning when failedNot scoredTechnical SearchAI DiscoveryMachine Readability
- What this checks
- Whether the returned HTML contains at least one h1 element.
- Why it matters
- A visible top-level heading helps visitors, assistive technology and automated readers identify the page subject. This is a MaxiMarket content-structure recommendation.
- How to fix
- Mark up the main page heading, such as the product name, as an <h1>.
- Expected
- The page has an h1 element that names its main content.
- Applies to
- Every retrieved page. Non-scoring: a MaxiMarket recommendation.
- Authority
- MaxiMarket recommendation · MaxiMarket best practiceMaxiMarket recommendation. No search engine, standard or platform requires this.
- Technical Score
- Not scoredA MaxiMarket recommendation; Google says there is no ideal heading structure.
- How MaxiMarket detects it
- Reports when the returned HTML contains no h1 element. Headings created by client-side JavaScript are visible only in browser-based audits.
- Sources
- WCAG 2.2 Understanding SC 1.3.1 Info and Relationships — W3C, verified 2026-09-26
- SEO Starter Guide — Google Search Central, verified 2026-09-26
Structured data (general)
STRUCTURED-JSONLD-003JSON-LD declares a usable typeStructured dataWarning when failedNot scoredTechnical SearchAI DiscoveryMachine Readability
- What this checks
- Whether valid JSON-LD declares at least one usable @type.
- Why it matters
- Schema.org organizes its vocabulary as types with associated properties, and structured data features are defined per type. MaxiMarket flags untyped JSON-LD because consumers cannot tell what it describes.
- How to fix
- Add an @type with a Schema.org type name to each entity in the JSON-LD.
- Expected
- Each structured data entity declares a Schema.org type, such as Product.
- Applies to
- Pages with at least one valid JSON-LD block.
- Authority
- MaxiMarket recommendation · MaxiMarket best practiceMaxiMarket recommendation. No search engine, standard or platform requires this.
- Technical Score
- Not scoredA MaxiMarket recommendation; untyped JSON-LD is not invalid.
- How MaxiMarket detects it
- Reports when at least one JSON-LD block is valid but no normalized @type name is found within the bounded traversal.
- Sources
- Schema.org data model — Schema.org, verified 2026-09-26
Crawl control and crawler access
CRAWL-ACCESS-005Search crawlers are not restricted only by the wildcard groupIndexingInfo when failedNot scoredTechnical SearchAI Discovery
- What this checks
- Whether Googlebot or Bingbot is disallowed for the audited URL through the User-agent: * group because no group of its own names it.
- Why it matters
- A crawler without its own group follows the * group. A broad * rule written for scrapers or AI crawlers then restricts search crawlers too, often unintentionally. This explains the cause of the restriction; the restriction itself is reported and scored once by its own rule.
- How to fix
- If search crawlers should crawl the page, add a group for them, for example "User-agent: Googlebot" and "User-agent: Bingbot" with the rules you intend (an empty "Disallow:" allows everything), and keep the restrictive rules in the * group for other bots.
- Expected
- Search crawler access is stated explicitly: a group that names the crawler, or a * group that does not restrict the page.
- Applies to
- Every retrieved page whose origin returned robots.txt or 404/410 for it; not evaluated when robots.txt is unavailable, returns a server error or exceeds the inspection limits.
- Authority
- MaxiMarket recommendation · MaxiMarket best practiceMaxiMarket diagnostic recommendation; informational and not scored.
- Technical Score
- Not scoredDiagnostic: the restriction is already reported and scored by CRAWL-ACCESS-001 (Googlebot) or CRAWL-ACCESS-004 (Bingbot), so it is never penalized twice.
- How MaxiMarket detects it
- The Googlebot (CRAWL-ACCESS-001) and Bingbot (CRAWL-ACCESS-004) evaluations; reported when either crawler is disallowed and no group names it, so the * group applied. Not evaluated when robots.txt is unavailable, answers 5xx, or exceeds the inspection limits; a 404/410 robots.txt allows everything.
- Sources
- RFC 9309: Robots Exclusion Protocol — IETF, verified 2026-09-26
- How Google interprets the robots.txt specification — Google Search Central, verified 2026-09-26
- To crawl or not to crawl, that is BingBot's question — Microsoft Bing (Bing Webmaster Blog), verified 2026-10-01