Audit

Audit Standard / 2026.3

Rule explorer: Audit Standard 2026.3

Every check that defines technical readiness in MaxiMarket Audit Standard 2026.3, 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.

Superseded. This is an earlier Audit Standard version, kept unchanged so audits saved under it keep their meaning. New audits use the current Audit Standard 2026.4.

Guides by topic: technical SEO audit rules, AI readiness, structured data and ecommerce product data.

Version
2026.3
Status
Superseded
Published
2026-09-30
Rules
92
Scored
72
Observations
33

Authority levels

Official search-engine requirement
A search engine documents it as required for a specific outcome, such as Google eligibility.
Strongest external authority
Open standard / Schema.org
Defined by an open standard or vocabulary: HTML, WCAG, IETF RFCs, Schema.org, Sitemaps, Open Graph.
Official platform recommendation
Recommended in official platform documentation, such as Google Search Central or an AI platform.
Accepted best practice
Widely accepted practice with a cited source, but no official requirement.
MaxiMarket recommendation
MaxiMarket’s own advice. Never presented as a search engine or platform requirement.
MaxiMarket methodology

Filter

Showing 0 rules and 21 observations.

Observations

Observations are neutral facts. They are never pass or fail, never warnings, and never part of the Technical Score.

ACCESS-CHALLENGE-001Observation · not scoredRetrieval without a challengeAI crawler access and policyTechnical SearchAI Discovery
What is reported
Whether MaxiMarket received the page content (retrieved) or an access-control, bot-challenge or authentication page (blocked). Reported also for blocked results.
Why it is not a rule
MaxiMarket's network and user agent are not a search crawler's, so a block here is evidence, not proof that crawlers are blocked.
Sources
ACCESS-STATUS-001Observation · not scoredStatus of the blocking responseAI crawler access and policyTechnical SearchAI Discovery
What is reported
For blocked results only: whether the challenge or access-denied response used an error status (error-status) or a success status (success-status).
Why it is not a rule
Only blocked results are concerned, and they are never evaluated as pages.
Sources
INDEX-NOINDEX-002Observation · not scoredCrawler-specific indexing exclusionsIndexing and snippet directivesTechnical SearchAI Discovery
What is reported
The crawler names (for example googlebot) that receive noindex or none through a crawler-named robots meta element or a user-agent-prefixed X-Robots-Tag directive. Present only when at least one exists.
Why it is not a rule
Excluding a page for one crawler is a policy choice, not a technical defect.
Sources
INDEX-SNIPPET-001Observation · not scoredSnippet restrictionsIndexing and snippet directivesTechnical SearchAI Discovery
What is reported
The snippet-restricting rules declared for any crawler: nosnippet, max-snippet (any value other than -1), max-image-preview-none, max-video-preview (any value other than -1), and data-nosnippet when elements use it. Present only when at least one exists.
Why it is not a rule
Snippet restrictions (which also remove eligibility for Google AI features) are an owner's choice.
Sources
INDEX-BING-AI-001Observation · not scoredBing AI answer and training controlsIndexing and snippet directivesAI Discovery
What is reported
The noarchive and nocache robots rules declared for all crawlers or for bingbot. Present only when at least one exists.
Why it is not a rule
These controls are a policy choice; their current Copilot behavior is not verifiable.
Sources
SEO-CANONICAL-009Observation · not scoredSelf-referencing canonicalCanonicalizationTechnical SearchAI Discovery
What is reported
For pages with a parseable canonical: whether it resolves (ignoring fragments) to the final URL (self) or to another URL (other).
Why it is not a rule
A canonical pointing elsewhere is often correct, for example for parameter variants.
Sources
SEM-MAIN-001Observation · not scoredMain landmarksHeadings and semantic structureAI DiscoveryMachine Readability
What is reported
The number of main elements and elements with role="main".
Why it is not a rule
A main landmark is one sufficient WCAG technique for exposing structure, not a requirement.
Sources
RENDER-TEXT-001Observation · not scoredText in the initial HTMLRendering and JavaScriptTechnical SearchAI Discovery
What is reported
The number of characters of text (whitespace collapsed) in the body of the HTML as served, outside script, style, template and noscript. Not reported for browser audits, which inspect the rendered document.
Why it is not a rule
Any threshold for "enough" text would be a MaxiMarket heuristic.
Sources
STRUCTURED-JSONLD-001Observation · not scoredJSON-LD blocksStructured data (general)Technical SearchAI DiscoveryMachine Readability
What is reported
The number of JSON-LD script blocks in the returned HTML.
Why it is not a rule
Not every page needs structured data, and Microdata or RDFa are not detected.
Sources
STRUCTURED-BREADCRUMB-003Observation · not scoredBreadcrumbs on deep pagesEntity and site identityTechnical SearchAI DiscoveryMachine Readability
What is reported
For pages other than the home page: whether a BreadcrumbList is declared.
Why it is not a rule
Breadcrumb markup is a MaxiMarket recommendation for deep pages.
Sources
INDEX-ROBOTSTXT-001Observation · not scoredrobots.txtCrawl control and crawler accessTechnical SearchAI Discovery
What is reported
Whether robots.txt at the final origin is present, not found (404 or 410), answered a server error, or was otherwise unavailable.
Why it is not a rule
robots.txt is optional; without it crawlers may access any resource.
Sources
CRAWL-ROBOTSTXT-004Observation · not scoredrobots.txt fields beyond the common setCrawl control and crawler accessTechnical SearchAI Discovery
What is reported
For retrieved robots.txt files: the field names other than user-agent, allow, disallow and sitemap (for example crawl-delay), possibly none.
Why it is not a rule
Support for other fields differs by crawler: Google ignores crawl-delay while Anthropic honors it.
Sources
CRAWL-SITEMAP-REF-001Observation · not scoredSitemap references in robots.txtCrawl control and crawler accessTechnical SearchAI Discovery
What is reported
For retrieved robots.txt files: whether at least one Sitemap line is declared.
Why it is not a rule
robots.txt is one documented way to publish sitemaps, not a requirement.
Sources
AI-TRAINING-POLICY-001Observation · not scoredAI training crawler policyAI crawler access and policyAI Discovery
What is reported
For the audited URL and each AI training token (GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, CCBot, Meta-ExternalAgent): allowed or disallowed by a group naming the token, or allowed-by-default or disallowed-by-default through the * group or the absence of rules. Present when robots.txt was retrieved or returned 404/410 and could be fully inspected.
Why it is not a rule
Training opt-out is an owner's policy choice, never a defect, and it is separate from search access.
Sources
AI-USER-FETCH-001Observation · not scoredRules for user-initiated AI fetchersAI crawler access and policyAI Discovery
What is reported
For retrieved robots.txt files: the user-initiated fetchers named in a group (chatgpt-user, claude-user, perplexity-user, meta-externalfetcher, google-agent, google-read-aloud), possibly none.
Why it is not a rule
OpenAI, Perplexity, Meta and Google say these fetchers may not apply robots.txt; Anthropic says Claude-User honors it.
Sources
AI-LLMSTXT-001Observation · not scored/llms.txtAI crawler access and policyAI Discovery
What is reported
Whether /llms.txt at the final origin is present in the proposed Markdown form (starting with a "# " heading), returns other content, is not found, or is unavailable.
Why it is not a rule
An emerging proposal that no documented AI platform requires; Google states no AI text files are needed.
Sources
INDEX-SITEMAP-001Observation · not scoredXML sitemapSitemapsTechnical SearchAI Discovery
What is reported
Whether a selected sitemap was found, all were not found, none could be selected, or retrieval was otherwise unavailable.
Why it is not a rule
Google recommends sitemaps only for some sites, which the audit cannot determine.
Sources
INDEX-SITEMAP-008Observation · not scoredPage listed in a sitemapSitemapsTechnical SearchAI Discovery
What is reported
Whether the page's canonical URL (or final URL) appears in an inspected urlset (listed), or not in any when every selected sitemap was a fully inspected urlset (not-listed).
Why it is not a rule
Absence may be an inspection-limit artifact on larger sites.
Sources
SOCIAL-OG-SITENAME-001Observation · not scoredOpen Graph site nameSocial metadataTechnical SearchAI DiscoverySocial Discovery
What is reported
Whether og:site_name is present, for pages that declare any well-formed og:* meta property.
Why it is not a rule
og:site_name is optional in the Open Graph protocol.
Sources