Every one of the 481 checks AudEsto's audit engine runs, in one place -- what each check actually looks at, and why it matters for search engines and AI answer engines. Use it to understand a result on your report, or to learn the reasoning behind the score before you run an audit at all.
Run a free audit and every result links straight back to the matching section here.
Every parameter the Single Page Audit evaluates for one URL. Report "Learn more" links land here.
Response, indexability, head tags, mobile, URL, server performance, resources and security for one URL.
Fix these with the related AudEsto toolsWhat it is: The final HTTP status the URL returns after any redirects.
Why it matters: Only pages that return 200 can be indexed and ranked; 4xx/5xx pages drop out of search.
What it is: How many redirect hops the requested URL passes through before reaching its final destination.
Why it matters: Every hop adds latency and can leak link signals; long chains may not be followed at all.
What it is: Whether the redirects used are permanent (301/308) or temporary (302/303/307).
Why it matters: Temporary redirects tell search engines to keep the old URL indexed instead of consolidating onto the new one.
What it is: Hard error statuses and "soft 404" pages that return 200 but say the page was not found.
Why it matters: Soft 404s waste crawl effort and get treated as thin pages; real missing pages should return 404/410.
What it is: Whether the final page is delivered over an encrypted HTTPS connection.
Why it matters: HTTPS is a ranking signal and browsers mark HTTP pages "Not secure".
Fix it: Website Safety CheckerWhat it is: noindex directives in the robots meta tag, googlebot meta tag or X-Robots-Tag header.
Why it matters: A noindex directive removes the page from search results no matter how good it is.
What it is: A page-level nofollow that tells crawlers not to follow any link on the page.
Why it matters: It stops the page from passing link signals to the pages it links to.
What it is: Robots directives sent in the HTTP response header rather than in the HTML.
Why it matters: Header directives are easy to miss in a CMS and can silently block indexing.
What it is: The value of the robots meta tag in the page head.
Why it matters: It controls indexing and link following for this specific page.
What it is: Whether the site’s robots.txt rules allow Googlebot to crawl this exact URL (longest-match rules, wildcards supported).
Why it matters: A blocked URL cannot be crawled, so its content can’t be evaluated or ranked properly.
What it is: Whether this exact URL appears in the XML sitemap(s) listed in robots.txt or at standard locations.
Why it matters: Listing canonical URLs in the sitemap helps discovery and signals which URL form you prefer.
Fix it: Sitemap GeneratorWhat it is: Presence, count and format of the rel="canonical" link element.
Why it matters: The canonical tells search engines which URL to index when the same content is reachable at several URLs.
What it is: Whether the canonical points to this URL itself or to another URL.
Why it matters: A canonical pointing elsewhere asks search engines not to index this URL.
What it is: Whether an HTTPS page’s canonical points to an http:// URL.
Why it matters: An insecure canonical sends conflicting signals about the preferred URL.
What it is: Presence of a <title> element in the head.
Why it matters: The title is the main clickable headline in search results and a core relevance signal.
Fix it: Meta Tags GeneratorWhat it is: Whether more than one <title> element is present.
Why it matters: Multiple titles leave it to the search engine to pick one, often the wrong one.
What it is: Presence of a meta description element.
Why it matters: Without one, search engines write their own snippet from page text.
Fix it: Meta Tags GeneratorWhat it is: Presence and value of the viewport meta tag (width=device-width).
Why it matters: Without it phones render a zoomed-out desktop layout, which fails mobile usability.
Fix it: Website Responsiveness CheckerWhat it is: The character encoding declared in the HTML or the HTTP header.
Why it matters: A missing or wrong charset can garble characters in results and on the page.
What it is: The lang attribute on the <html> element and whether it is a valid language code.
Why it matters: It helps search engines and screen readers handle the page’s language correctly.
What it is: hreflang annotations for language/region alternates, including validity, self-reference and x-default.
Why it matters: Correct hreflang shows the right language version to each audience; broken sets are ignored.
What it is: Whether the layout viewport matches the device width.
Why it matters: Google indexes the mobile version of pages first; a non-responsive viewport hurts mobile rankings.
Fix it: Website Responsiveness CheckerWhat it is: A combined mobile check: responsive viewport, zoom allowed, responsive CSS media queries, no horizontal overflow and readable text.
Why it matters: Most searches happen on phones and Google uses mobile-first indexing.
Fix it: Website Responsiveness CheckerWhat it is: Whether the viewport disables pinch-to-zoom (user-scalable=no or maximum-scale=1).
Why it matters: Blocking zoom is an accessibility failure for visitors who need larger text.
What it is: Total character length of the final URL.
Why it matters: Short URLs are easier to read and share and are less likely to be truncated in results.
What it is: Lowercase, hyphen-separated, parameter-light URL paths without session IDs or deep nesting.
Why it matters: Clean URLs are easier to crawl, share and understand.
What it is: Whether the slug is made of readable words rather than opaque IDs.
Why it matters: Descriptive slugs reinforce relevance and improve click-through from results.
What it is: Whether this URL follows the trailing-slash convention used by the site’s own sitemap.
Why it matters: Mixing /page and /page/ creates duplicate URLs that split signals.
What it is: Whether the server negotiates HTTP/2 (ALPN) or advertises HTTP/3.
Why it matters: Newer protocols load pages with many resources noticeably faster.
Fix it: Page Speed TestWhat it is: Whether the HTML is served with Brotli or gzip compression.
Why it matters: Compression typically cuts HTML transfer size by 70% or more.
Fix it: Page Speed TestWhat it is: The Content-Type header and whether its charset agrees with the HTML.
Why it matters: Conflicting encodings can cause garbled text and parsing problems.
What it is: Cache-Control, ETag and Last-Modified headers on the HTML document.
Why it matters: Validators let browsers and CDNs revalidate cheaply instead of re-downloading.
What it is: Whether CSS, JS and images are cached for at least 7 days.
Why it matters: Long caching makes repeat visits and navigation between pages much faster.
Fix it: Page Speed TestWhat it is: Time to first byte of the HTML document.
Why it matters: A slow server delays every other loading step, including Largest Contentful Paint.
Fix it: Page Speed TestWhat it is: Time until the page finished loading (browser render) or the HTML finished downloading.
Why it matters: Slow pages lose visitors and weaken Core Web Vitals.
Fix it: Page Speed TestWhat it is: Uncompressed size of the HTML document.
Why it matters: Heavy HTML slows parsing; Googlebot only processes the first 2 MB of an HTML file.
What it is: Number of elements in the page and the maximum nesting depth.
Why it matters: Large DOMs slow rendering, styling and interaction responsiveness.
What it is: Number of scripts, stylesheets, images, fonts and iframes the page requests.
Why it matters: Every request adds overhead, especially on mobile networks.
Fix it: Page Speed TestWhat it is: Synchronous scripts and stylesheets in the <head> that block first paint.
Why it matters: Blocking resources delay the moment visitors see anything on screen.
Fix it: Page Speed TestWhat it is: Largest Contentful Paint, Cumulative Layout Shift and Total Blocking Time from lab measurement.
Why it matters: Core Web Vitals are Google’s page experience metrics and a ranking signal.
Fix it: Page Speed TestWhat it is: Uncaught errors while rendering and script files that fail to load.
Why it matters: Broken scripts can hide content, break menus and stop tracking.
What it is: Stylesheets that fail to load, are served with the wrong type or look malformed.
Why it matters: Broken CSS causes layout problems and unstyled content.
What it is: Whether the main content is present in the server HTML or only appears after JavaScript runs.
Why it matters: Many crawlers and AI bots don’t run JavaScript, and Google renders it with a delay.
What it is: HTTP resources loaded by an HTTPS page.
Why it matters: Browsers block active mixed content and show security warnings for passive mixed content.
Fix it: Website Safety CheckerWhat it is: Internal links and social URLs that still point at http:// versions of the site.
Why it matters: They cause redirect hops and inconsistent URL signals.
What it is: Images on the page that return errors.
Why it matters: Broken images look unprofessional and waste requests.
What it is: Whether below-the-fold images are lazy-loaded and the top images are not.
Why it matters: Lazy-loading the hero image delays LCP; eager-loading everything wastes bandwidth.
What it is: Whether images declare width and height attributes.
Why it matters: Declared dimensions reserve space and prevent layout shift (CLS).
What it is: Whether the first (hero) image loads eagerly, ideally with fetchpriority="high".
Why it matters: The hero image is usually the LCP element; prioritising it speeds up perceived load.
What it is: The Strict-Transport-Security header.
Why it matters: HSTS forces HTTPS on return visits and protects against downgrade attacks.
Fix it: Website Safety CheckerWhat it is: X-Content-Type-Options, clickjacking protection, Content-Security-Policy, Referrer-Policy and Permissions-Policy.
Why it matters: They protect visitors and signal a well-maintained site.
Fix it: Website Safety CheckerWhat it is: Whether the submitted URL points to a public, internet-reachable address.
Why it matters: Private or internal addresses cannot be audited.
What it is: Whether the page could be downloaded at all.
Why it matters: If the page can’t be fetched, search engines likely have trouble too.
What it is: Whether the URL returns an HTML document rather than a file or API response.
Why it matters: Only HTML pages can be evaluated for SEO and AEO.
What it is: Whether the HTML response actually contains content.
Why it matters: An empty document has nothing to index.
Title, meta description, headings, content and images of the page.
Fix these with the related AudEsto toolsWhat it is: Whether the page has a title and what it says.
Why it matters: The title is the strongest on-page relevance signal and the headline in search results.
Fix it: Meta Tags GeneratorWhat it is: Character and approximate pixel width of the title.
Why it matters: Titles over ~580 px (about 60 characters) are truncated in results.
Fix it: Meta Tags GeneratorWhat it is: Whether the title contains the target keyword or detected primary topic.
Why it matters: Search engines and users use the title to judge whether the page matches the query.
What it is: Whether the main topic appears near the start of the title.
Why it matters: Front-loaded terms carry more weight and survive truncation.
What it is: Unnatural repetition of words in the title.
Why it matters: Stuffed titles look spammy and can be rewritten or demoted.
What it is: Capitalisation, separators and punctuation in the title.
Why it matters: Readable titles earn more clicks.
What it is: Whether the page has a meta description.
Why it matters: A good description is your ad copy in search results.
Fix it: Meta Tags GeneratorWhat it is: Length of the meta description.
Why it matters: Around 120-160 characters fits without truncation.
Fix it: Meta Tags GeneratorWhat it is: Whether the description mentions the main topic.
Why it matters: Matching query terms are bolded in snippets, which lifts click-through.
What it is: Distinctness from the title, full sentences, a call to action and no truncating quotes.
Why it matters: A compelling snippet increases clicks at the same ranking.
What it is: Presence of an H1 heading.
Why it matters: The H1 tells visitors and search engines what the page is about.
What it is: How many H1 headings the page has.
Why it matters: One H1 gives a clear main topic; several dilute it.
What it is: Character length of the H1.
Why it matters: Very short or very long H1s describe the page poorly.
What it is: How closely the H1 and the title describe the same thing.
Why it matters: Aligned title and H1 confirm the page topic.
What it is: Whether the H1 includes the main topic.
Why it matters: The H1 is a strong on-page relevance signal.
What it is: Number of H2 subheadings relative to content length.
Why it matters: Subheadings make long content scannable and easy to extract.
What it is: Whether long H2 sections are broken up with H3s.
Why it matters: Nested headings give a clear outline of subtopics.
What it is: Whether heading levels descend without skipping (H2 → H3 → H4).
Why it matters: A logical outline helps search engines, AI systems and screen readers.
What it is: Heading tags with no text.
Why it matters: Empty headings break the document outline.
What it is: Whether the H1 comes before other headings in the source.
Why it matters: The outline should start with the page’s main heading.
What it is: Words in the main content (navigation, header and footer excluded).
Why it matters: Pages need enough substance to satisfy the query.
Fix it: Content Readability CheckerWhat it is: Share of the HTML that is visible main-content text.
Why it matters: Very low ratios point to markup bloat or thin content.
What it is: Whether a <main>/<article> element marks the primary content.
Why it matters: Semantic containers help crawlers separate content from boilerplate.
What it is: Word count compared with what the detected search intent usually needs.
Why it matters: Informational queries need depth; transactional pages can be shorter.
What it is: Flesch Reading Ease and grade level of the main content.
Why it matters: Easy-to-read content keeps visitors engaged.
Fix it: Content Readability CheckerWhat it is: Average sentence length and share of sentences over 25 words.
Why it matters: Long sentences are harder to read, especially on mobile.
Fix it: Content Readability CheckerWhat it is: Average paragraph length and very long paragraphs.
Why it matters: Short paragraphs are easier to scan.
Fix it: Content Readability CheckerWhat it is: Share of content sections that reference the main topic.
Why it matters: Sections that drift from the topic weaken relevance.
What it is: Whether the main topic appears in the first 100 words.
Why it matters: Early mention confirms relevance to readers and search engines.
What it is: Density of the main keyword and the most repeated word.
Why it matters: Over-optimised text reads badly and can trigger spam filters.
Fix it: Keyword Density CheckerWhat it is: Very low word count, few paragraphs or highly repetitive wording.
Why it matters: Thin pages rarely rank and can drag down perceived site quality.
What it is: Whether the page delivers what the detected intent expects.
Why it matters: Pages that mismatch intent rarely rank for the query.
What it is: The most recent published/modified date found and its age.
Why it matters: Fresh, maintained content is preferred for many queries.
What it is: Whether an author byline is shown.
Why it matters: Named authors support credibility, especially on articles.
What it is: Bulleted and numbered lists in the main content.
Why it matters: Lists make content scannable and easy to use in featured snippets.
What it is: Tables in the main content.
Why it matters: Tables present comparisons and data in an extractable way.
What it is: Question-and-answer content on the page.
Why it matters: FAQs capture question-style searches and conversational queries.
What it is: Number of images, and how many are in the main content.
Why it matters: Relevant images improve engagement and understanding.
What it is: Images with no alt attribute.
Why it matters: Alt text makes images understandable to search engines and screen readers.
What it is: Alt texts that are filenames, generic, repeated or too long.
Why it matters: Descriptive alt text improves image search and accessibility.
What it is: Images larger than 200 KB.
Why it matters: Heavy images slow the page, especially on mobile.
Fix it: Page Speed TestWhat it is: Share of images in modern formats (WebP, AVIF, SVG).
Why it matters: Modern formats are much smaller at the same quality.
What it is: Whether content images offer srcset/sizes or <picture> sources.
Why it matters: Phones download appropriately sized images instead of desktop ones.
What it is: Whether key images have captions.
Why it matters: Captions give images context for readers and search engines.
Structured data on the page: formats, syntax, types relevant to this page and their properties.
Fix these with the related AudEsto toolsWhat it is: Whether any structured data (JSON-LD, Microdata or RDFa) is on the page.
Why it matters: Structured data lets search and AI systems understand entities directly and unlocks rich results.
What it is: Number of JSON-LD blocks.
Why it matters: JSON-LD is Google’s recommended structured data format.
What it is: Microdata items (itemscope/itemtype) on the page.
Why it matters: Shown for completeness; it is valid but harder to maintain than JSON-LD.
What it is: RDFa items (typeof) on the page.
Why it matters: Shown for completeness; RDFa is valid but less common.
What it is: Whether every JSON-LD block is valid JSON with a schema.org @context.
Why it matters: Invalid blocks are ignored entirely.
What it is: All schema.org types found on the page.
Why it matters: Shows how the page describes itself to machines.
What it is: Which schema types this kind of page (article, product, homepage, local business...) should carry, and which are missing.
Why it matters: The right types make the page eligible for the matching rich results.
What it is: Required properties missing from the detected schema types.
Why it matters: Types missing required properties are not eligible for rich results.
What it is: Recommended properties missing from the detected types.
Why it matters: Extra properties give search engines a fuller picture.
What it is: Whether entities reference each other (WebPage → isPartOf → WebSite, Article → publisher → Organization).
Why it matters: A connected graph clarifies who published what.
What it is: Stable @id identifiers and whether references resolve.
Why it matters: Consistent @ids let search engines merge information about the same entity.
What it is: Whether page-level schema URLs use this site’s host.
Why it matters: Leftover staging or old-domain URLs confuse entity understanding.
What it is: The Organization/LocalBusiness entity and its name and logo.
Why it matters: It identifies the business behind the page and feeds knowledge panels.
What it is: Links from the entity to its official profiles (social, Wikipedia, Wikidata).
Why it matters: sameAs helps search engines confirm the entity’s identity.
What it is: The WebSite entity.
Why it matters: It declares the site name used in search results.
What it is: A WebPage (or subtype) entity describing the page.
Why it matters: It anchors the page as an entity in the graph.
What it is: Article schema on article-type pages.
Why it matters: It enables article rich results and clarifies authorship and dates.
What it is: The author property on the Article.
Why it matters: Tells search engines who wrote the content.
What it is: The publisher property on the Article.
Why it matters: Tells search engines which organisation published it.
What it is: The datePublished property on the Article.
Why it matters: Gives the original publication date.
What it is: The dateModified property on the Article.
Why it matters: Signals when the content was last updated.
What it is: The mainEntityOfPage property on the Article.
Why it matters: Confirms the article is the page’s main entity.
What it is: The image property on the Article.
Why it matters: A representative image is needed for article rich results.
What it is: Product schema and the completeness of its offer (price, currency, availability).
Why it matters: It enables price and availability in results and merchant listings.
What it is: Breadcrumb structured data on non-home pages.
Why it matters: Results show a readable path instead of the raw URL.
Fix it: Breadcrumb Schema GeneratorWhat it is: Sequential positions, names and item URLs in the BreadcrumbList.
Why it matters: Malformed breadcrumbs are ignored.
Fix it: Breadcrumb Schema GeneratorWhat it is: FAQPage markup for visible questions and answers.
Why it matters: It makes Q&A content explicit for search and AI engines.
What it is: Whether every Question has an acceptedAnswer with text.
Why it matters: Incomplete questions are invalid.
What it is: LocalBusiness schema with address, phone, hours and geo.
Why it matters: It feeds local results and map listings.
What it is: Service schema on service pages.
Why it matters: It describes the offering, provider and area served.
What it is: A Person entity describing the author.
Why it matters: It connects the content to a real, verifiable author.
What it is: Ratings with ratingValue and a review/rating count.
Why it matters: Incomplete ratings are not eligible for review stars.
What it is: ImageObject entities and their URLs.
Why it matters: Images need a url or contentUrl to be usable.
Whether this individual page sufficiently covers the topic it appears to target.
Fix these with the related AudEsto toolsWhat it is: The main topic the page targets (the target keyword, or detected from title, H1 and content).
Why it matters: Every other semantic check is measured against this topic.
What it is: Named entities (brands, products, people, places, standards) that recur in the content.
Why it matters: Specific entities anchor the topic for search and AI systems.
What it is: Supporting entities around the main subject.
Why it matters: Context entities show depth of knowledge.
What it is: Vocabulary that co-occurs with the primary topic.
Why it matters: Experts use a predictable set of related terms; missing them signals shallow coverage.
What it is: Primary topic presence in title, H1, opening, meta description, URL and subheadings.
Why it matters: Prominent placement confirms what the page is about.
What it is: Whether the brand/entity is named consistently across title, Open Graph and schema.
Why it matters: Inconsistent names make it harder to connect the page to the right entity.
What it is: Share of content sections that stay on the topic or its related terms.
Why it matters: Off-topic sections dilute relevance.
What it is: Related terms developed across several sections rather than mentioned once.
Why it matters: Developed subtopics signal comprehensive coverage.
What it is: Subtopics that pages with the detected intent usually cover.
Why it matters: Covering expected concepts satisfies more of the searcher’s needs.
What it is: Expected subtopics not found on the page.
Why it matters: Gaps are often exactly where competitors outrank you.
What it is: Whether the page provides what its intent expects (explanations, comparisons, pricing, contact details...).
Why it matters: Intent mismatch is one of the most common reasons pages fail to rank.
What it is: Subheadings followed by fewer than 40 words.
Why it matters: Headings that promise a topic but barely cover it frustrate readers.
What it is: Word count, number of substantive sections, lists/tables and media.
Why it matters: Deeper coverage tends to satisfy more queries.
What it is: A blend of depth, subtopic coverage, related-term development and on-topic sections.
Why it matters: Comprehensive pages rank for more queries and are cited more by AI.
What it is: Share of paragraphs that use the topic’s vocabulary.
Why it matters: Paragraphs that drift off topic weaken the page.
What it is: Sentences that mention several key entities together.
Why it matters: Explaining how entities relate supports knowledge-graph style understanding.
What it is: Reading grade level versus a target for the detected intent.
Why it matters: Content should match the reading level of its audience.
Fix it: Content Readability CheckerWhat it is: Vocabulary diversity and filler phrases.
Why it matters: Varied, natural wording reads better and avoids looking auto-generated.
Links on this page only - presence, placement, anchor text and link health.
Fix these with the related AudEsto toolsWhat it is: Whether the page links to other pages on the same site.
Why it matters: Pages with no internal links are dead ends for users and crawlers.
What it is: Total and unique internal links on the page.
Why it matters: Internal links distribute authority and help discovery.
What it is: Total and unique outbound links.
Why it matters: Relevant outbound links can support credibility.
What it is: Total number of links on the page.
Why it matters: Very high link counts dilute each link and overwhelm users.
What it is: Internal links visible in the first screen (or in the opening content).
Why it matters: Early links get more clicks and highlight priority pages.
What it is: Internal links inside the body content rather than navigation.
Why it matters: In-content links carry the most context and weight.
What it is: Contextual links whose anchor or target URL shares vocabulary with the page topic.
Why it matters: Links between related pages reinforce topical relevance.
What it is: Share of links with meaningful anchor text.
Why it matters: Anchor text tells users and search engines what the target page is about.
Fix it: Broken Link CheckerWhat it is: Links with no text, aria-label or image alt.
Why it matters: Empty anchors give no context and fail accessibility.
What it is: "Click here", "read more" and similar anchors.
Why it matters: Generic anchors waste the link’s context.
What it is: Naked URL anchors, over-long anchors and repeated exact-match anchors.
Why it matters: Concise, varied anchors look natural.
What it is: Internal links on this page that return errors.
Why it matters: Broken links waste crawl effort and frustrate users.
Fix it: Broken Link CheckerWhat it is: Outbound links on this page that return errors.
Why it matters: Dead outbound links make content look unmaintained.
Fix it: Broken Link CheckerWhat it is: Internal links that point at redirecting URLs.
Why it matters: Linking directly to the final URL avoids extra hops.
What it is: Internal links marked rel="nofollow".
Why it matters: Nofollow on internal links wastes internal link equity.
What it is: Links that only work through JavaScript or only exist after rendering.
Why it matters: Crawlers reliably follow only real <a href> links in the HTML.
Open Graph and Twitter/X card tags and how shared links will preview.
Fix these with the related AudEsto toolsWhat it is: The Open Graph title.
Why it matters: It is the headline of shared links on Facebook, LinkedIn and messaging apps.
Fix it: Open Graph TesterWhat it is: The Open Graph description.
Why it matters: It is the summary under shared links.
Fix it: Open Graph TesterWhat it is: The Open Graph URL.
Why it matters: It is the canonical URL that collects shares.
Fix it: Open Graph TesterWhat it is: The Open Graph object type (website, article, product).
Why it matters: It tells platforms how to present the content.
Fix it: Open Graph TesterWhat it is: The Open Graph image.
Why it matters: Posts with an image get far more engagement.
Fix it: Open Graph TesterWhat it is: The Open Graph site name.
Why it matters: It shows the brand on the card.
Fix it: Open Graph TesterWhat it is: Declared share image dimensions.
Why it matters: Platforms can render the card before downloading the image.
Fix it: Open Graph TesterWhat it is: Whether the share image URL is publicly reachable and returns an image.
Why it matters: Platforms silently drop images they can’t fetch.
Fix it: Open Graph TesterWhat it is: The actual pixel size of the share image.
Why it matters: Around 1200×630 displays well everywhere; smaller images become thumbnails.
Fix it: Open Graph TesterWhat it is: Length of the social title and description.
Why it matters: Over-long text is truncated on cards.
Fix it: Open Graph TesterWhat it is: The Twitter/X card type.
Why it matters: It selects the preview layout on X.
Fix it: Open Graph TesterWhat it is: The Twitter/X title (falls back to og:title).
Why it matters: Controls the headline on X.
Fix it: Open Graph TesterWhat it is: The Twitter/X description (falls back to og:description).
Why it matters: Controls the summary on X.
Fix it: Open Graph TesterWhat it is: The Twitter/X image (falls back to og:image).
Why it matters: Controls the image on X.
Fix it: Open Graph TesterWhat it is: The brand’s @handle.
Why it matters: Attributes the card to your account.
What it is: The author’s @handle.
Why it matters: Attributes the card to the author.
What it is: How closely og:title matches the page title.
Why it matters: Consistent messaging avoids confusing people who click through.
What it is: How closely og:description matches the meta description.
Why it matters: Consistent messaging across search and social.
What it is: Whether og:url matches the canonical URL.
Why it matters: Shares consolidate on one URL.
What it is: Whether any share image is declared.
Why it matters: Shared links without an image get fewer clicks.
What it is: Share of the core Open Graph/Twitter tags present.
Why it matters: Complete tags give you control over every share.
Fix it: Open Graph TesterObservable Experience, Expertise, Authority and Trust signals on the page.
Fix these with the related AudEsto toolsWhat it is: First-person accounts of using, testing or doing the thing described.
Why it matters: Experience is the first "E" in E-E-A-T; first-hand content is hard to fake.
Fix it: E-E-A-T CheckerWhat it is: Concrete examples in the content.
Why it matters: Specific examples show real understanding.
What it is: Own data, measurements or survey results.
Why it matters: Original data is a strong reason to trust and cite a page.
What it is: Case studies, success stories or client results.
Why it matters: Results prove expertise in practice.
What it is: Images, video or step-by-step instructions in the main content.
Why it matters: Showing the process proves hands-on knowledge.
What it is: Measurements, results and proof points.
Why it matters: Evidence backs up claims.
What it is: Statements about the author’s or team’s experience.
Why it matters: Relevant experience supports credibility.
What it is: Whether an author is named on the page or in schema.
Why it matters: Anonymous content is harder to trust, especially on YMYL topics.
Fix it: E-E-A-T CheckerWhat it is: Degrees, certifications or job titles for the author.
Why it matters: Credentials support expertise on specialist topics.
What it is: An author bio on the page.
Why it matters: A bio explains why the author is qualified.
What it is: Links to an author profile page or external profiles.
Why it matters: Profiles let readers and search engines verify the author.
What it is: Quotes from or references to recognised experts.
Why it matters: Expert input strengthens authority.
What it is: Outbound links to sources in the main content, especially authoritative ones.
Why it matters: Citing sources shows research and supports trust.
What it is: Numeric or research claims versus citations provided.
Why it matters: Unsupported statistics undermine credibility.
What it is: Whether the organisation behind the page is identified.
Why it matters: Readers and search engines want to know who is responsible for the content.
What it is: A link to an About/company page.
Why it matters: About pages are a key trust signal.
What it is: Whether the author’s identity connects to a profile or external accounts.
Why it matters: Verifiable authors are more trustworthy.
What it is: Publisher declared with name and logo in schema.
Why it matters: It connects content to a recognisable brand.
What it is: Number of external references in the content.
Why it matters: References show the content is grounded in wider sources.
What it is: Business certifications, licences, awards or memberships.
Why it matters: Credentials build trust for commercial pages.
What it is: Contact details or a link to a contact page.
Why it matters: Being reachable is a basic trust signal.
What it is: A link to a privacy policy.
Why it matters: Expected on any legitimate site, required in many regions.
What it is: A link to terms or legal information.
Why it matters: Signals a legitimate, accountable business.
What it is: Editorial policy, review, fact-checking or methodology statements.
Why it matters: Shows how content is produced and kept accurate.
What it is: Whether a publication or update date is exposed.
Why it matters: Readers need to know how current the information is.
What it is: Credits for data, quotes and images.
Why it matters: Attribution is honest and builds trust.
What it is: Disclosure of affiliate or sponsored links when present.
Why it matters: Undisclosed affiliate links erode trust and may breach advertising rules.
What it is: Whether the page is delivered securely.
Why it matters: A secure connection is a baseline trust requirement.
Fix it: Website Safety CheckerWhat it is: Copyright holder or company name on the page.
Why it matters: Clear ownership shows who stands behind the content.
How easily answer engines and generative search can extract, trust and cite the page.
Fix these with the related AudEsto toolsWhat it is: Questions and headings followed immediately by a short, self-contained answer.
Why it matters: Answer engines lift the first clear answer they find.
What it is: Headings phrased as questions.
Why it matters: They mirror how people ask assistants and search.
What it is: Paragraphs of 30-80 words.
Why it matters: Snippet-length passages are easy to quote as answers.
What it is: "X is a..." definition sentences for the main topic.
Why it matters: Definitions are one of the most common AI answer formats.
What it is: Numbered steps, lists and tables.
Why it matters: Structured content maps directly to step and comparison answers.
What it is: Specific, number-bearing statements.
Why it matters: AI answers quote precise facts.
What it is: Linked sources and data tables backing claims.
Why it matters: Evidence makes the page safer for AI to cite.
What it is: In-line attributions such as "according to...".
Why it matters: Attributed facts are more trustworthy to answer engines.
What it is: Main entity defined early and brand identified consistently.
Why it matters: Clear entities reduce ambiguity for language models.
What it is: Coverage of who, what, when, where and why/how.
Why it matters: Answers need enough context to stand on their own.
What it is: Pronoun-led paragraphs and undefined acronyms.
Why it matters: Passages quoted out of context lose meaning if they start with "It" or use unexplained acronyms.
What it is: Share of sections that open with a standalone summary sentence.
Why it matters: Standalone openings can be quoted without the surrounding text.
What it is: Number of questions the page addresses.
Why it matters: Covering real questions captures conversational queries.
What it is: Whether each question is answered in its first sentence.
Why it matters: Direct answers are preferred by answer engines.
What it is: A dedicated FAQ section, FAQPage schema or accordions.
Why it matters: Groups conversational Q&A in an extractable block.
What it is: Whether answers are 25-300 words.
Why it matters: Answers must be complete yet short enough to quote.
What it is: Whether answers reuse the key terms of their questions.
Why it matters: Aligned answers are recognised as answering that question.
What it is: Common questions for the intent that the page doesn’t appear to answer.
Why it matters: Unanswered questions are opportunities for competitors to be cited instead.
What it is: First-hand findings, data or experience.
Why it matters: Unique information is the main reason an AI engine cites one page over another.
What it is: Conclusions, recommendations and takeaways.
Why it matters: Clear insights give AI answers something to attribute to you.
What it is: References to sources in the content.
Why it matters: Pages that cite sources are treated as more reliable sources themselves.
What it is: Whether both the author and the publishing organisation are identified.
Why it matters: Generative engines weigh who wrote and published a source.
What it is: Consistent naming of the brand/entity across the page and metadata.
Why it matters: Consistency helps models attribute content to the right entity.
What it is: Subheadings with lists or tables inside sections.
Why it matters: Chunked content is easier to segment and retrieve.
What it is: Sentences that connect key entities.
Why it matters: Explicit relationships help models answer accurately.
What it is: One H1 and H2/H3 nesting without skipped levels.
Why it matters: A clean outline maps directly to answer sections.
What it is: Whether the subject is unambiguous from the title, H1 and opening.
Why it matters: Ambiguous pages are less likely to be retrieved for the right queries.
What it is: Whether the brand behind the content is identifiable.
Why it matters: Brand recognition supports citation and trust.
What it is: Author named and described with Person schema.
Why it matters: Machine-readable authorship supports trust in generative results.
What it is: Organization declared as a machine-readable entity.
Why it matters: It connects the content to a known organisation.
What it is: Whether statistics name their source.
Why it matters: Unattributed statistics are risky for AI to repeat.
What it is: Surveys, experiments or original analysis.
Why it matters: Original research is the strongest reason to be cited.
What it is: Short, standalone, fact-bearing sentences.
Why it matters: Crisp sentences are easy to quote verbatim.
What it is: Overall depth and breadth of topic coverage.
Why it matters: Comprehensive pages are used as sources for multi-part answers.
Every check the Sitewide (entire website) Audit runs across up to 500 crawled pages, grouped into the 24 analysed areas. Report "Learn more" links land here.
How much of the site search engines can crawl and index.
Fix these with the related AudEsto toolsWhat it is: Pages carrying a noindex directive in the robots or googlebot meta tag.
Why it matters: A noindex page is dropped from search results no matter how good it is - right for thank-you or filter pages, wrong for pages meant to rank.
What it is: URLs that send a noindex directive in the X-Robots-Tag HTTP header.
Why it matters: Header directives are invisible in the HTML and are often set by a server or CDN rule by mistake.
What it is: Pages that show "not found" style content while answering HTTP 200.
Why it matters: Search engines may index the error page, and real missing pages should return 404/410.
Fix it: Bulk HTTP Status CheckerWhat it is: Pages whose raw HTML is an app shell with almost no text until JavaScript runs.
Why it matters: Search engines render JavaScript later and less reliably; most AI crawlers do not render it at all.
What it is: Pages more than 3 clicks away from the home page.
Why it matters: Deep pages are crawled less often and receive less internal link equity.
What it is: URLs listed in the XML sitemap that no crawled page links to. On a partial crawl (limit reached) the result is informational.
Why it matters: Orphans are hard for crawlers to discover and receive no internal link signals.
Fix it: Orphan Page CheckerWhat it is: Crawled pages that cannot be reached by following links from the home page.
Why it matters: Pages outside the navigation graph are crawled rarely and rank poorly.
What it is: Crawled URLs answering 401/403.
Why it matters: Linking public visitors and crawlers to protected URLs wastes crawl budget.
What it is: URLs that could not be fetched at all (connection errors, timeouts).
Why it matters: Unreachable URLs cannot be indexed; persistent errors point to server problems.
What it is: Discovered URLs disallowed by robots.txt.
Why it matters: Blocked URLs are not crawled; linking to them or listing them in the sitemap sends mixed signals.
Fix it: Robots.txt GeneratorWhat it is: The share of crawled HTML pages that are indexable.
Why it matters: A low share means most crawled pages can never rank - usually a noindex, canonical or template mistake.
Response codes of every crawled URL and the links that point at errors.
Fix these with the related AudEsto toolsWhat it is: Crawled URLs that answer 400-499 (404, 410, ...).
Why it matters: Error pages drop out of search and waste the links pointing to them.
Fix it: Bulk HTTP Status CheckerWhat it is: Crawled URLs that answer 500-599.
Why it matters: Persistent server errors get pages removed from the index.
Fix it: Bulk HTTP Status CheckerWhat it is: Links on crawled pages that point to internal URLs returning an error.
Why it matters: Broken links frustrate visitors and leak link equity into dead ends.
Fix it: Broken Link CheckerWhat it is: Internal links that go through a redirect before reaching the page.
Why it matters: Each hop adds latency and dilutes signals; link straight to the final URL.
What it is: URLs that redirect two or more times before resolving.
Why it matters: Chains slow crawling and may not be followed to the end.
What it is: Redirect chains with four or more hops.
Why it matters: Googlebot follows a limited number of hops; long chains can stop indexing.
What it is: URLs that redirect back to themselves or loop between URLs.
Why it matters: A loop never resolves, so the page is unreachable for users and crawlers.
What it is: Outbound links whose destination answers 4xx/5xx (social share buttons and bot-blocking answers are ignored).
Why it matters: Dead outbound links hurt user trust and signal an unmaintained site.
Fix it: Broken Link CheckerWhat it is: Error URLs that are still linked from crawled pages.
Why it matters: Fixing or removing these links recovers the equity they waste.
Whether robots.txt exists, is valid and blocks only what it should.
Fix these with the related AudEsto toolsWhat it is: Whether /robots.txt exists and is readable.
Why it matters: robots.txt is where crawl rules and the sitemap location are declared.
Fix it: Robots.txt GeneratorWhat it is: The site has no robots.txt file.
Why it matters: Without it crawlers assume everything is allowed and cannot find the sitemap location.
Fix it: Robots.txt GeneratorWhat it is: robots.txt could not be fetched (no response).
Why it matters: The check is reported as unverified rather than missing.
What it is: Lines that are not valid "field: value" directives or use unknown fields.
Why it matters: Invalid lines are ignored by crawlers, so the intended rule never applies.
Fix it: Robots.txt GeneratorWhat it is: Whether robots.txt contains a Sitemap: line.
Why it matters: It is the standard way for every crawler to find the sitemap.
What it is: "Disallow: /" in the rules for all user-agents.
Why it matters: It blocks every search engine from crawling the site.
What it is: The same path both allowed and disallowed for one user-agent.
Why it matters: Conflicting rules are resolved unpredictably across crawlers.
What it is: Sitemap URLs that robots.txt disallows.
Why it matters: The sitemap asks for indexing while robots.txt forbids crawling.
What it is: Blocked URLs that are well linked or listed in the sitemap.
Why it matters: These are usually accidental blocks of pages that should rank.
What it is: robots.txt blocks a large share of discovered URLs.
Why it matters: Over-blocking hides content that could rank.
What it is: Rules that block CSS, JavaScript or images.
Why it matters: Search engines need these files to render pages as users see them.
Availability, format and coverage of the XML sitemap and the health of its URLs.
Fix these with the related AudEsto toolsWhat it is: A readable XML sitemap (or sitemap index) was found.
Why it matters: The sitemap tells search engines which URLs you want indexed.
Fix it: Sitemap GeneratorWhat it is: No sitemap was found in robots.txt or the standard locations.
Why it matters: Without it, discovery relies entirely on links.
Fix it: Sitemap GeneratorWhat it is: Sitemap files that could not be fetched or are not valid XML.
Why it matters: Broken files are ignored, so their URLs are not submitted.
What it is: Listed URLs that answer a client error.
Why it matters: Dead URLs in a sitemap reduce trust in the whole file.
What it is: Listed URLs that answer a server error.
Why it matters: Server errors on submitted URLs slow crawling of the site.
What it is: Listed URLs that redirect.
Why it matters: A sitemap should list final destination URLs only.
What it is: Listed URLs disallowed by robots.txt.
Why it matters: Search engines cannot crawl URLs you ask them to index.
What it is: Listed URLs that carry noindex.
Why it matters: Conflicting signals; remove them from the sitemap.
What it is: Listed URLs that canonicalize to a different URL.
Why it matters: Only canonical URLs belong in the sitemap.
What it is: Indexable crawled pages missing from the sitemap.
Why it matters: Complete coverage speeds up discovery of new and updated pages.
Fix it: Sitemap GeneratorWhat it is: Sitemap URLs not linked internally (reference only - scored under Crawl & Indexability).
Why it matters: See Orphan pages.
What it is: lastmod values that are not W3C dates or lie in the future.
Why it matters: Search engines ignore invalid dates.
What it is: Sitemap entries without lastmod dates.
Why it matters: Accurate lastmod helps search engines recrawl changed pages sooner.
What it is: The sitemap is not declared in robots.txt.
Why it matters: Declaring it lets every crawler find it.
How much crawl budget goes to URLs that can never rank.
Fix these with the related AudEsto toolsWhat it is: Share of crawled URLs that are redirects, errors, duplicates or non-indexable.
Why it matters: Crawl budget spent on these URLs is not spent on pages that can rank.
What it is: URLs that differ only in case, trailing slash, tracking or session parameters.
Why it matters: Every variant is crawled separately and splits signals.
What it is: Calendar paths, repeating segments, stacked filters or session IDs.
Why it matters: They can generate endless URLs that exhaust crawl budget.
What it is: Single paths that produce many parameter variations.
Why it matters: Uncontrolled parameters create near-infinite duplicate URLs.
What it is: Thin URLs that are noindexed, paginated or filtered.
Why it matters: They consume crawl resources without ranking potential.
What it is: Identical content served under different addresses.
Why it matters: Search engines must pick one version - often not the one you want.
What it is: Internal links to redirecting, noindexed or parameterised URLs.
Why it matters: Linking to canonical, indexable URLs focuses crawling where it matters.
Whether canonical tags consistently point search engines to the right URL.
Fix these with the related AudEsto toolsWhat it is: Pages without a rel="canonical" tag.
Why it matters: A self-referencing canonical protects against duplicate URL variants.
What it is: Canonicals pointing to 4xx/5xx URLs.
Why it matters: Search engines ignore the canonical and may drop the page.
What it is: Canonicals pointing to redirecting URLs.
Why it matters: Use the final URL as the canonical.
What it is: Canonicals pointing to pages that are noindex.
Why it matters: Contradictory signals that can remove both pages from search.
What it is: A → B → C canonical sequences.
Why it matters: Point every page straight at the final canonical.
What it is: Pages that canonicalize to each other.
Why it matters: Search engines ignore looping canonicals.
What it is: Canonicals pointing to another domain.
Why it matters: Correct for syndication, harmful when accidental.
What it is: Pages with more than one canonical tag.
Why it matters: Conflicting canonicals are usually all ignored.
What it is: Canonicalized URLs listed in the sitemap.
Why it matters: List only canonical URLs in the sitemap.
What it is: Internal links pointing to non-canonical URLs.
Why it matters: Link to the canonical version so signals are not split.
Click depth, hierarchy, hub pages and how link equity flows.
Fix these with the related AudEsto toolsWhat it is: High-PageRank pages more than 3 clicks deep.
Why it matters: Your strongest pages should be close to the home page.
Fix it: Silo Structure CheckerWhat it is: Pages reachable through only one internal link.
Why it matters: One broken link would orphan them; more paths spread equity.
What it is: Navigation-level targets linked from nearly all pages.
Why it matters: Make sure these are your most important pages.
What it is: Pages whose parent folder URL has no crawlable page.
Why it matters: Hub pages per folder make the hierarchy navigable for users and crawlers.
Fix it: Silo Structure CheckerWhat it is: Groups of pages not connected to the home page.
Why it matters: Disconnected sections are discovered late and receive no equity.
What it is: Small groups of pages linking only to each other.
Why it matters: Crawlers entering them find nothing new.
What it is: Number of internal pages linked from the home page.
Why it matters: A weak home hub makes the whole site deeper.
What it is: Whether hub pages link to every page of a topic.
Why it matters: Hubs organise topics and pass equity to their pages.
Fix it: Silo Structure CheckerInternal link counts, placement, anchor text and links into non-indexable pages.
Fix these with the related AudEsto toolsWhat it is: Crawled pages no other page links to.
Why it matters: Pages without internal links are treated as unimportant.
Fix it: Orphan Page CheckerWhat it is: Pages with a single internal link pointing at them.
Why it matters: More contextual links strengthen weak pages.
What it is: Pages with more than 150 outgoing internal links.
Why it matters: Too many links dilute the value each one passes.
What it is: Key pages without contextual links and at most two links overall.
Why it matters: Your important pages should be the best linked.
What it is: Internal links pointing to noindex pages.
Why it matters: They spend equity on pages that cannot rank.
What it is: Internal links pointing to non-canonical URLs.
Why it matters: Link to the canonical version instead.
What it is: Internal links with rel="nofollow".
Why it matters: It throws away internal link equity and can stop discovery.
What it is: Links with anchors like "click here" or "read more".
Why it matters: Descriptive anchors tell search engines what the target is about.
What it is: Text links with no anchor text.
Why it matters: Empty anchors give no context to users, screen readers or crawlers.
What it is: One anchor used for three or more different destinations.
Why it matters: It blurs which page is about that topic.
What it is: Pages whose incoming in-content anchors are mostly one identical keyword phrase (anchors that are simply the page title are not counted).
Why it matters: Unnaturally uniform anchors look manipulative.
Pages and URLs whose content duplicates other pages of the site.
Fix these with the related AudEsto toolsWhat it is: Pages with identical main content.
Why it matters: Duplicates split signals and waste crawl budget.
What it is: Pages whose content is almost identical (SimHash comparison).
Why it matters: Near-duplicates compete with each other; merge or differentiate them.
What it is: Pages with substantially similar content.
Why it matters: Substantial overlap weakens each page’s uniqueness.
What it is: The same address reachable in several forms (http/https, www, slash, case, parameters).
Why it matters: Redirect variants to one normalised URL.
What it is: Print-friendly or AMP copies of pages.
Why it matters: Canonicalise them to the main page.
What it is: Paginated pages repeating the first page’s title.
Why it matters: Add "Page N" so each page is distinct.
What it is: Duplicate pages that are also under 300 words.
Why it matters: Thin duplicates are the first candidates for removal or merging.
What it is: Duplicate pages pointing at different canonicals.
Why it matters: All copies should agree on one canonical URL.
Titles and meta descriptions compared across every page.
Fix these with the related AudEsto toolsWhat it is: Pages without a usable <title>.
Why it matters: The title is the main headline in search results.
Fix it: Meta Tags GeneratorWhat it is: Titles used on more than one page.
Why it matters: Duplicate titles make pages compete and confuse users.
Fix it: Meta Tags GeneratorWhat it is: Titles that are almost identical.
Why it matters: Nearly identical titles blur which page answers which query.
What it is: Titles under 30 characters.
Why it matters: Short titles waste space that could describe the page.
Fix it: Meta Tags GeneratorWhat it is: Titles over 60 characters.
Why it matters: Long titles get truncated in results.
Fix it: Meta Tags GeneratorWhat it is: Pages with more than one <title>.
Why it matters: Search engines may choose the wrong one.
What it is: Pages without a meta description.
Why it matters: Search engines then write their own snippet.
Fix it: Meta Tags GeneratorWhat it is: Descriptions used on more than one page.
Why it matters: Unique descriptions improve click-through.
Fix it: Meta Tags GeneratorWhat it is: Descriptions that are almost identical.
Why it matters: Differentiate them per page.
What it is: Descriptions under 70 characters.
Why it matters: Too short to sell the click.
What it is: Descriptions over 160 characters.
Why it matters: They get truncated in results.
What it is: Pages sharing both title and description with another page.
Why it matters: A strong sign of template duplication.
What it is: Duplicate titles concentrated in one URL template.
Why it matters: Fix the title pattern once in the template.
What it is: Duplicate descriptions concentrated in one URL template.
Why it matters: Fix the description pattern once in the template.
H1 and heading structure compared across every page.
Fix these with the related AudEsto toolsWhat it is: Pages without an H1.
Why it matters: The H1 states the page topic for users and search engines.
Fix it: Heading Tags CheckerWhat it is: Pages with more than one H1.
Why it matters: One clear H1 is the strongest topic signal.
Fix it: Heading Tags CheckerWhat it is: H1s shared by several pages.
Why it matters: Unique H1s help differentiate pages.
Fix it: Heading Tags CheckerWhat it is: Long pages without H2 subheadings.
Why it matters: Subheadings make long content scannable and extractable.
Fix it: Heading Tags CheckerWhat it is: Jumps such as H2 → H4.
Why it matters: A clean outline helps accessibility and passage understanding.
Fix it: Heading Tags CheckerWhat it is: Heading tags without text.
Why it matters: Empty headings break the document outline.
What it is: Pages with far more headings than the content warrants.
Why it matters: Headings used for styling dilute the outline.
What it is: Duplicate H1s concentrated in one URL template.
Why it matters: Fix the H1 pattern in the template.
What it is: Headings repeated on most pages (template headings).
Why it matters: Informational: make sure template headings are not the main headings.
Word counts, boilerplate, freshness and topic coverage across the site.
Fix these with the related AudEsto toolsWhat it is: Indexable pages with under 20 words of main content.
Why it matters: Empty pages are low quality and waste crawl budget.
Fix it: Content Readability CheckerWhat it is: Pages with under 100 words.
Why it matters: Very thin pages rarely satisfy a search.
Fix it: Content Readability CheckerWhat it is: Pages with 100-299 words.
Why it matters: Expanding them with useful detail improves rankings.
Fix it: Content Readability CheckerWhat it is: Pages where main content is under 25% of the words.
Why it matters: Template text dominates and the page looks thin.
What it is: Pages with no identifiable main content area.
Why it matters: Search engines struggle to find what the page is about.
What it is: Thin pages that are also barely linked.
Why it matters: Improve, merge or noindex them.
What it is: Articles not updated in three or more years.
Why it matters: Freshness matters for many topics; refresh and update dateModified.
What it is: Articles without a publication date.
Why it matters: Dates help users and search engines judge freshness.
What it is: Topics mentioned across many pages with no dedicated page.
Why it matters: A dedicated supporting page can capture that demand.
Pages that compete with each other for the same topic and intent.
Fix these with the related AudEsto toolsWhat it is: Pages sharing the same primary topic and search intent.
Why it matters: Competing pages split rankings; pick one primary page per topic.
Fix it: Keyword Density CheckerBroken, oversized and inaccessible images across the site.
Fix these with the related AudEsto toolsWhat it is: Images that return 4xx/5xx.
Why it matters: Broken images hurt user experience and image search.
Fix it: Image SEO AnalyzerWhat it is: Images without an alt attribute.
Why it matters: Alt text is needed for accessibility and image search.
Fix it: Image SEO AnalyzerWhat it is: Images with alt="" (decorative).
Why it matters: Correct for decorative images only.
What it is: The same alt text reused across different images.
Why it matters: Each image should be described individually.
What it is: Image files larger than 300 KB.
Why it matters: Large images slow pages, especially on mobile.
Fix it: Image SEO AnalyzerWhat it is: Images without width/height attributes.
Why it matters: Missing dimensions cause layout shift (CLS).
What it is: Image URLs that redirect.
Why it matters: Reference the final file URL.
What it is: Share of images served as WebP or AVIF.
Why it matters: Modern formats are much smaller for the same quality.
Fix it: Image SEO AnalyzerWhat it is: Share of images with srcset/picture.
Why it matters: Phones then download appropriately sized files.
What it is: Share of images with loading="lazy".
Why it matters: Deferring below-the-fold images speeds up the first view.
What it is: Image files linked but never embedded.
Why it matters: Informational: they may be leftovers.
Length, parameters, casing and consistency of every URL.
Fix these with the related AudEsto toolsWhat it is: URLs with query parameters.
Why it matters: Parameters create duplicate variants and dilute signals.
What it is: URLs with three or more parameters.
Why it matters: Often filter combinations that should not be crawled.
What it is: URLs longer than 100 characters.
Why it matters: Short descriptive URLs are easier to share and read.
What it is: URLs longer than 200 characters.
Why it matters: Very long URLs can be truncated or ignored.
What it is: URLs containing uppercase letters.
Why it matters: Case variants can create duplicates.
What it is: URLs using underscores as word separators.
Why it matters: Hyphens are the recommended word separator.
What it is: URLs containing random IDs or hashes.
Why it matters: Readable slugs describe the content.
What it is: URLs carrying session identifiers.
Why it matters: Session IDs create endless duplicate URLs.
What it is: Internal URLs carrying utm_/gclid parameters.
Why it matters: Tracking on internal links creates duplicates and skews analytics.
What it is: URLs that normalise to the same address.
Why it matters: Pick one form and redirect the rest.
What it is: URLs using a different protocol than the site.
Why it matters: Link to the HTTPS version everywhere.
Fix it: Website Safety CheckerWhat it is: URLs using a different host variant.
Why it matters: Mixed hosts split signals between two copies of the site.
What it is: URLs nested more than four folders deep.
Why it matters: Flatter hierarchies are easier to crawl and understand.
What it is: Whether URLs consistently use or omit the trailing slash.
Why it matters: Inconsistent slashes create duplicate URLs.
Paginated series, filter URLs and crawl traps.
Fix these with the related AudEsto toolsWhat it is: Paginated pages with no internal links.
Why it matters: Later pages of a series become undiscoverable.
What it is: rel next/prev links pointing to error pages.
Why it matters: Broken series stop crawlers mid-way.
What it is: Paginated pages repeating the first page’s title.
Why it matters: Distinct titles help each page stand alone.
What it is: Faceted/filter URLs that are indexable.
Why it matters: Filter combinations flood the index with near-duplicates.
What it is: Filter URLs with no canonical strategy.
Why it matters: Canonicalise to the unfiltered category.
What it is: Robots-blocked filter URLs that are linked internally.
Why it matters: Links to blocked URLs waste equity.
What it is: URLs that look like crawl traps.
Why it matters: Traps can consume the entire crawl budget.
What it is: Pages that spawn many filter URLs.
Why it matters: Limit crawlable facet combinations.
hreflang annotations and language targeting.
Fix these with the related AudEsto toolsWhat it is: Whether the site uses hreflang (single-language sites need none).
Why it matters: Informational.
What it is: Pages without <html lang>.
Why it matters: It declares the page language to search engines and assistive tech.
What it is: Pages lacking hreflang while others have it.
Why it matters: Incomplete sets are ignored.
What it is: Language/region codes that are not ISO codes.
Why it matters: Invalid codes are ignored.
What it is: Language versions that do not link back to each other.
Why it matters: hreflang must be reciprocal to work.
What it is: hreflang pointing to redirecting URLs.
Why it matters: Point to final URLs.
What it is: hreflang pointing to error pages.
Why it matters: Broken alternates are dropped.
What it is: hreflang pointing to noindex pages.
Why it matters: Alternates must be indexable.
What it is: hreflang pages canonicalized elsewhere.
Why it matters: Each language version should be its own canonical.
What it is: hreflang sets without x-default.
Why it matters: x-default tells search engines the fallback version.
What it is: hreflang targets whose page language differs from the code.
Why it matters: Mismatches send users to the wrong language.
HTTPS, redirects, certificate and security headers that affect search.
Fix these with the related AudEsto toolsWhat it is: Whether the site is served over HTTPS.
Why it matters: HTTPS is a ranking signal and browsers warn on HTTP.
Fix it: Website Safety CheckerWhat it is: Crawled URLs served over plain HTTP.
Why it matters: Every page should be on HTTPS.
Fix it: Website Safety CheckerWhat it is: Whether http:// requests redirect to https://.
Why it matters: Without it, an insecure copy of the site stays reachable.
Fix it: Website Safety CheckerWhat it is: Certificate validity and expiry from a real TLS handshake.
Why it matters: An invalid certificate blocks visitors with a browser warning.
Fix it: Website Safety CheckerWhat it is: HTTPS pages loading resources over HTTP.
Why it matters: Browsers block or warn about mixed content.
Fix it: Website Safety CheckerWhat it is: Internal links to http:// URLs.
Why it matters: They cause redirects and mixed signals.
What it is: Canonicals pointing to http:// URLs.
Why it matters: Canonicals should use the HTTPS URL.
What it is: Strict-Transport-Security coverage.
Why it matters: HSTS forces browsers to use HTTPS.
Fix it: Website Safety CheckerWhat it is: Both www and non-www answer 200 without redirecting.
Why it matters: Two copies of the site split signals.
What it is: CSP, X-Content-Type-Options and Referrer-Policy coverage.
Why it matters: Trust and hardening signals (low SEO weight).
Fix it: Website Safety CheckerGoogle PageSpeed Insights results for representative pages (not part of the SEO score).
Fix these with the related AudEsto toolsWhat it is: Average PageSpeed Insights mobile score of tested pages.
Why it matters: Slow pages lose visitors; Core Web Vitals are a ranking signal.
Fix it: Page Speed TestWhat it is: Tested pages failing Core Web Vitals in real-user data.
Why it matters: Field data is what Google uses for page experience.
Fix it: Page Speed TestWhat it is: Tested pages with LCP above 2.5 s.
Why it matters: LCP measures how fast the main content appears.
Fix it: Page Speed TestWhat it is: Tested pages with INP above 200 ms.
Why it matters: INP measures responsiveness to user input.
Fix it: Page Speed TestWhat it is: Tested pages with CLS above 0.1.
Why it matters: Layout shifts frustrate users and cause mis-clicks.
Fix it: Page Speed TestHow consistently structured data is implemented across the site.
Fix these with the related AudEsto toolsWhat it is: Share of pages with structured data.
Why it matters: Structured data enables rich results and helps machines understand pages.
Fix it: Schema Markup GeneratorWhat it is: Pages whose JSON-LD does not parse.
Why it matters: Invalid blocks are ignored entirely.
Fix it: Schema Markup GeneratorWhat it is: Schema objects missing required properties.
Why it matters: Rich results need the required properties.
Fix it: Schema Markup GeneratorWhat it is: Schema objects missing recommended properties.
Why it matters: Recommended properties make results richer.
Fix it: Schema Markup GeneratorWhat it is: Pages declaring the same singleton type twice.
Why it matters: Duplicate blocks can conflict.
What it is: Pages declaring different organization names.
Why it matters: Conflicting entities confuse knowledge graphs.
What it is: Organization/LocalBusiness schema on the home page.
Why it matters: It anchors the brand entity.
Fix it: Schema Markup GeneratorWhat it is: How many different organization names are used.
Why it matters: One consistent name and @id build entity trust.
What it is: WebSite schema on the home page.
Why it matters: It declares the site name.
Fix it: Schema Markup GeneratorWhat it is: Inner pages with BreadcrumbList schema.
Why it matters: Breadcrumbs show hierarchy in results.
Fix it: Breadcrumb Schema GeneratorWhat it is: Articles with Article/BlogPosting schema.
Why it matters: Enables article rich results.
Fix it: Schema Markup GeneratorWhat it is: Product pages with Product schema.
Why it matters: Enables price and availability in results.
Fix it: Schema Markup GeneratorWhat it is: Address/phone found without LocalBusiness schema.
Why it matters: Helps local search understanding.
Fix it: Schema Markup GeneratorWhat it is: Authored articles describing the author with Person schema.
Why it matters: Author entities support E-E-A-T.
Fix it: Schema Markup GeneratorWhat it is: URL templates where no page carries schema.
Why it matters: Adding schema to the template covers every page at once.
Authorship, identity and trust signals as patterns across the site.
Fix these with the related AudEsto toolsWhat it is: Whether an About page exists and is linked.
Why it matters: It tells users and search engines who is behind the site.
Fix it: E-E-A-T CheckerWhat it is: Contact page or contact details.
Why it matters: Reachable publishers are more trustworthy.
Fix it: E-E-A-T CheckerWhat it is: Whether a privacy policy exists.
Why it matters: A basic trust and legal requirement.
Fix it: E-E-A-T CheckerWhat it is: Whether terms/legal pages exist.
Why it matters: A trust signal for users and reviewers.
Fix it: E-E-A-T CheckerWhat it is: Articles naming their author.
Why it matters: Named, credible authors support expertise.
Fix it: E-E-A-T CheckerWhat it is: Articles showing a publication date.
Why it matters: Dates show freshness and accountability.
What it is: Articles citing external sources.
Why it matters: Citations support factual claims.
What it is: Articles with first-hand experience signals.
Why it matters: Experience is the first E in E-E-A-T.
What it is: Whether authors have profile pages.
Why it matters: Profiles show credentials and connect content to people.
Fix it: E-E-A-T CheckerWhat it is: Author names written in different ways.
Why it matters: Consistent names build author entities.
What it is: Whether an editorial/review policy is published.
Why it matters: Shows how content is researched and maintained.
What it is: Whether the organization is named consistently.
Why it matters: A consistent entity builds trust.
What it is: Share of titles using the same brand suffix.
Why it matters: Consistent branding reinforces recognition.
How well AI answer engines can read, quote and cite the site.
Fix these with the related AudEsto toolsWhat it is: Pages with content in HTML, headings and enough text.
Why it matters: AI crawlers mostly do not run JavaScript and need clear structure.
Fix it: AI Content DetectorWhat it is: Pages with short direct answers under question headings or definitions.
Why it matters: Answer engines quote concise, self-contained passages.
What it is: Pages that open with a clear definition.
Why it matters: Definitions are the most-cited passage type.
What it is: Pages using lists and tables.
Why it matters: Structured content is easy to extract.
What it is: Pages citing sources.
Why it matters: Cited facts are more likely to be trusted and reused.
What it is: Pages containing original data and specifics.
Why it matters: Unique data earns citations.
What it is: Whether any page has FAQ content.
Why it matters: FAQs map directly to questions users ask assistants.
What it is: Question-style headings across the site.
Why it matters: Headings phrased as questions match conversational queries.
What it is: Whether /llms.txt is published.
Why it matters: It summarises the site and key pages for AI agents.
Fix it: LLMs.txt GeneratorWhat it is: Whether the brand entity is named consistently in schema.
Why it matters: Consistent entities are recognised by knowledge graphs.
What it is: Official profile links in Organization.sameAs.
Why it matters: They connect the brand to known entities.
What it is: How strongly pages within a topic link to each other.
Why it matters: Cohesive clusters build topical authority.
Fix it: Silo Structure CheckerWhat it is: Topics mentioned across pages without a dedicated page.
Why it matters: Supporting pages complete topical coverage.
What it is: Groups of pages covering the same topic.
Why it matters: Answer engines pick one source; consolidate authority.
Problems shared by most pages of one template, reported once.
Fix these with the related AudEsto toolsWhat it is: A problem shared by most pages (60%+) of one URL template.
Why it matters: It usually has a single fix in the template.
What it is: Links repeated in the navigation/footer of every page.
Why it matters: Very large sitewide menus dilute link equity.
What it is: No problem affects most pages of a template.
Why it matters: Informational.
The crawl aggregated into prioritised actions.
Fix these with the related AudEsto toolsWhat it is: High-PageRank pages affected by crawl, duplicate or technical problems.
Why it matters: Fixing your strongest pages has the biggest impact.
What it is: Long pages with no internal links (not shown on partial crawls).
Why it matters: Linking them is a quick way to unlock existing content.
What it is: Long-form pages with at most two internal links.
Why it matters: More internal links help them rank.
What it is: Long pages affected by indexing, duplicate or metadata problems.
Why it matters: Good content held back by fixable technical issues.
What it is: Low-effort fixes with measurable impact.
Why it matters: A good place to start.
Checks from the previous website audit engine, kept for reports created before the Sitewide Audit engine (v3.0).
Crawlability, security, performance, and the markup that lets search engines fetch and render a page at all.
Fix these with the Technical SEO toolsWhat it is: Confirms the site serves its pages over HTTPS rather than plain HTTP.
Why it matters: HTTPS is a confirmed Google ranking signal and browsers flag HTTP sites as "Not Secure," which erodes trust and click-through.
What it is: Checks that requests to the HTTP version of a URL 301-redirect to its HTTPS equivalent.
Why it matters: Without this redirect, search engines can index both HTTP and HTTPS copies of a page, splitting link equity and creating duplicate content.
What it is: Verifies the TLS certificate is currently valid, correctly chained, and issued for the requested domain.
Why it matters: An invalid certificate triggers browser security warnings that block most visitors before they ever see the page.
Fix it: Website Safety CheckerWhat it is: Tests whether the layout adapts cleanly at typical smartphone widths without horizontal scrolling or overlapping elements.
Why it matters: Google indexes and ranks primarily using the mobile version of a page (mobile-first indexing), so a broken phone layout directly hurts rankings.
Fix it: Website Responsiveness CheckerWhat it is: Tests whether the layout adapts correctly at tablet-range viewport widths.
Why it matters: A large and fast-growing share of traffic arrives on tablets; a layout that only works at phone or desktop widths loses that audience.
Fix it: Website Responsiveness CheckerWhat it is: Tests whether the layout holds up on wide desktop viewports without wasted whitespace or broken grids.
Why it matters: A layout that only tuned for mobile can look broken or unfinished on desktop, undermining credibility for the majority of B2B research traffic.
Fix it: Website Responsiveness CheckerWhat it is: Checks for a `<meta name="viewport">` tag that tells mobile browsers how to scale the page.
Why it matters: Without it, mobile browsers render the desktop layout and shrink it to fit, producing tiny unreadable text on phones.
What it is: Checks whether a robots.txt file exists at the domain root.
Why it matters: robots.txt is the standard place crawlers look for crawl directives and a sitemap pointer; its absence isn’t fatal but is a missed control point.
Fix it: Robots.txt GeneratorWhat it is: Parses robots.txt to confirm its directives (User-agent, Disallow, Allow, Sitemap) are syntactically valid.
Why it matters: A malformed robots.txt can be misread by crawlers, accidentally blocking pages that should be indexed or allowing ones that shouldn’t be.
Fix it: Robots.txt GeneratorWhat it is: Checks whether an XML sitemap exists at the expected location.
Why it matters: A sitemap gives search engines a direct, complete list of URLs to crawl instead of relying purely on discovering links.
Fix it: Sitemap GeneratorWhat it is: Measures how long the server takes to send the first byte of the response after a request.
Why it matters: TTFB is the floor under every other loading metric -- a slow server response delays everything downstream and is a direct Core Web Vitals input.
Fix it: Page Speed TestWhat it is: Checks whether the server compresses text responses (HTML/CSS/JS) with Brotli or Gzip.
Why it matters: Compression can cut transfer size by 70%+ with no quality loss, directly speeding up page load on every connection.
Fix it: Page Speed TestWhat it is: Checks how many days remain before the current TLS certificate expires.
Why it matters: An expired certificate takes the entire site offline behind browser warnings with no advance notice to visitors.
Fix it: Website Safety CheckerWhat it is: Measures how long DNS lookups for the domain take to resolve.
Why it matters: Slow DNS adds delay before a browser can even start connecting, on top of whatever the server itself takes to respond.
What it is: Checks whether HTTP response headers leak the server software and OS version.
Why it matters: Publishing exact server/OS versions gives attackers a head start matching known vulnerabilities to your stack.
Fix it: Website Safety CheckerWhat it is: Validates that any JSON-LD structured data on the page parses as well-formed JSON.
Why it matters: A syntax error in JSON-LD makes the entire schema block unreadable to search engines, silently losing any rich-result eligibility it was meant to provide.
Fix it: Schema Markup GeneratorWhat it is: Checks for a favicon linked or present at the conventional location.
Why it matters: Favicons appear in browser tabs, bookmarks, and search results; a missing one reads as unfinished or untrustworthy.
What it is: Checks for an apple-touch-icon link tag used when the site is saved to an iOS home screen.
Why it matters: Without it, iOS falls back to a generic screenshot-based icon instead of your brand mark for home-screen shortcuts.
What it is: Checks whether CSS files are minified (whitespace/comments stripped) rather than served as raw source.
Why it matters: Minification reduces file size and parse time with zero visual impact, a straightforward performance win.
What it is: Checks whether JavaScript files are minified rather than served as raw source.
Why it matters: Unminified JS ships unnecessary bytes and can meaningfully slow parsing and execution on slower devices.
What it is: Scans for meta robots or X-Robots-Tag headers set to noindex or nofollow.
Why it matters: A stray noindex tag -- often left over from staging -- silently removes an important page from search results entirely.
What it is: Measures how much CSS is written inline via `style` attributes rather than in stylesheets.
Why it matters: Heavy inline styling bloats HTML payload and blocks the browser from caching styles across pages.
What it is: Checks that the page declares a character encoding (typically UTF-8).
Why it matters: Without an explicit charset, browsers may guess wrong and render special characters, symbols, or non-Latin text as garbled glyphs.
What it is: Checks for an X-Frame-Options (or equivalent CSP frame-ancestors) header restricting who can embed the page in an iframe.
Why it matters: Without it, an attacker can frame your page inside their own site and trick users into clicking things they can’t see (clickjacking).
What it is: Checks for the `X-Content-Type-Options: nosniff` header.
Why it matters: Without it, browsers may reinterpret a file’s type based on content rather than its declared Content-Type, opening a path for disguised malicious files.
What it is: Checks whether a Content-Security-Policy header restricts which sources scripts, styles, and other resources can load from.
Why it matters: CSP is one of the strongest defenses against cross-site scripting (XSS) by blocking unauthorized script execution outright.
Fix it: Website Safety CheckerWhat it is: Checks for a `lang` attribute on the `<html>` tag declaring the page’s language.
Why it matters: Search engines and screen readers use this to serve the page to the right audience and pronounce content correctly.
What it is: Checks whether the page uses modern CSS Flexbox/Grid rather than legacy float- or table-based layout hacks.
Why it matters: Modern layout systems render more predictably across devices and are far easier to make genuinely responsive.
What it is: Checks for BreadcrumbList structured data marking up the page’s position in the site hierarchy.
Why it matters: Breadcrumb schema can make Google show a clean hierarchical path in search results instead of a raw URL, improving click-through.
Fix it: Breadcrumb Schema GeneratorWhat it is: Checks whether an AMP (Accelerated Mobile Pages) version of the page is linked, where applicable.
Why it matters: For publishers still relying on AMP surfaces, a missing or broken AMP link forfeits eligibility for those placements.
What it is: Checks that paginated content exposes real crawlable `<a href>` links between pages rather than JS-only pagination.
Why it matters: Crawlers that can’t click a "Next page" button rely on real anchor links to discover page 2, 3, and beyond.
What it is: Checks whether icons and simple graphics use SVG rather than raster images.
Why it matters: SVGs stay sharp at any size and are typically far smaller than an equivalent PNG, helping both quality and load time.
What it is: Checks for `<link rel="dns-prefetch">` hints for third-party domains the page connects to.
Why it matters: DNS prefetching resolves external hostnames early, shaving latency off requests to CDNs, fonts, and third-party scripts.
What it is: Measures how deeply nested and how large the page’s DOM tree is.
Why it matters: A bloated DOM slows down style recalculation and rendering, and is explicitly flagged by Lighthouse as a performance risk.
What it is: Checks an HTTPS page for resources (images, scripts, styles) still loaded over plain HTTP.
Why it matters: Mixed content triggers browser warnings and can be silently blocked, breaking images or scripts on an otherwise secure page.
Fix it: Website Safety CheckerWhat it is: Checks that a page’s canonical tag points to itself when there’s no duplicate to consolidate.
Why it matters: A missing or misdirected self-canonical leaves the page’s preferred URL ambiguous to search engines.
What it is: Checks that the server negotiates modern, strong TLS cipher suites rather than deprecated weak ones.
Why it matters: Outdated ciphers are vulnerable to known attacks and can trigger security warnings or reduced trust indicators in modern browsers.
What it is: Checks whether cookies are flagged Secure (HTTPS-only) and HttpOnly (inaccessible to JavaScript).
Why it matters: Without these flags, cookies can be intercepted over insecure connections or stolen via cross-site scripting.
Fix it: Website Safety CheckerWhat it is: Checks that links opening in a new tab (`target="_blank"`) include `rel="noopener"`.
Why it matters: Without `noopener`, the linked page can access and manipulate the original tab via `window.opener` -- a known phishing/security risk.
What it is: Checks for `<link rel="preload">` hints on assets critical to first render (hero image, key font, etc.).
Why it matters: Preloading tells the browser to fetch render-critical assets immediately instead of discovering them late in the parse, improving perceived load speed.
What it is: Measures total JavaScript payload size delivered to the page.
Why it matters: Heavy JS bundles delay interactivity and directly worsen Core Web Vitals metrics like Total Blocking Time.
What it is: Reports Largest Contentful Paint -- how long the largest visible element takes to render.
Why it matters: LCP is one of Google’s three Core Web Vitals and a direct ranking factor measuring perceived load speed.
Fix it: Page Speed TestWhat it is: Reports how long the main thread was blocked by long tasks, delaying responsiveness to input.
Why it matters: High TBT means the page looks loaded but doesn’t actually respond to clicks or taps, a common source of user frustration.
What it is: Measures how much visible content unexpectedly shifts position while the page loads.
Why it matters: CLS is a Core Web Vital; layout jumps cause mis-clicks and a jarring experience, and directly hurt rankings.
What it is: Checks how heavily the site relies on query-string parameters (`?sort=`, `?ref=`, etc.) to generate URLs.
Why it matters: Uncontrolled parameter combinations can multiply into near-duplicate URLs that waste crawl budget and dilute ranking signals.
What it is: Checks usage of `#fragment` anchor links for in-page navigation.
Why it matters: Hash-only routing (common in older single-page apps) can hide distinct content from crawlers that treat the fragment as the same URL.
What it is: Checks for a linked RSS or Atom feed, typically for blog/news content.
Why it matters: Feeds help syndication, aggregators, and some discovery/crawl pathways pick up new content quickly.
What it is: Counts elements using inline `style` attributes across the page.
Why it matters: Excessive inline styling increases HTML weight and makes consistent, cacheable styling harder to maintain.
What it is: Checks for hreflang tags declaring language/region-specific versions of a page.
Why it matters: Without hreflang, search engines can serve the wrong language version to users, or treat regional variants as duplicate content.
What it is: Measures how many clicks deep a page sits from the homepage in the site’s link structure.
Why it matters: Pages buried many clicks deep get crawled less often and receive less internal link equity, hurting their ranking potential.
What it is: Checks for a Strict-Transport-Security header forcing browsers to only ever connect over HTTPS.
Why it matters: HSTS closes the window for downgrade attacks by making the browser refuse HTTP entirely for future visits, even before a redirect can run.
Fix it: Website Safety CheckerWhat it is: Checks that the www and non-www versions of the domain don’t both resolve as separate, non-redirecting sites.
Why it matters: Two live versions of the same site split ranking signals and can be crawled and indexed as duplicate content.
What it is: Checks whether the server supports the modern HTTP/2 or HTTP/3 protocols instead of only HTTP/1.1.
Why it matters: Newer protocols multiplex requests over one connection, cutting latency meaningfully versus HTTP/1.1’s one-request-at-a-time model.
What it is: Detects URLs that redirect through multiple hops before reaching their final destination.
Why it matters: Each extra hop adds latency and wastes crawl budget; long chains can also cause crawlers to give up before reaching the final page.
What it is: Checks that canonical tags don’t point in a circular chain (A canonicalizes to B, B back to A).
Why it matters: A canonical loop gives search engines no clear signal for which URL is authoritative, and both can end up poorly indexed.
What it is: Reports that the audit itself was blocked from fetching the target because it resolved to a private, internal, or otherwise unsafe network address.
Why it matters: This protects against SSRF abuse; it also means the URL entered isn’t a normal public website reachable the way visitors and crawlers would reach it.
What it is: Confirms the domain itself (not just individual pages) is correctly served over HTTPS.
Why it matters: A domain-level HTTPS failure affects every page on the site at once and is one of the most basic trust and ranking prerequisites.
Fix it: Website Safety CheckerWhat it is: Confirms robots.txt is actually reachable at the domain root during a full site crawl.
Why it matters: If robots.txt can’t be fetched, crawlers may fall back to conservative default behavior instead of respecting your intended crawl rules.
Fix it: Robots.txt GeneratorWhat it is: Confirms a sitemap.xml is discoverable during a full site crawl, typically via robots.txt or the conventional path.
Why it matters: A missing sitemap forces search engines to rely entirely on link discovery, which can miss pages with weak internal linking.
Fix it: Sitemap GeneratorWhat it is: Counts crawled pages that returned a hard error status (4xx/5xx) across the whole site.
Why it matters: Error pages waste crawl budget, break the user journey, and can be a sign of a larger structural problem like a bad migration.
Fix it: Broken Link CheckerWhat it is: Checks a sample of crawled pages for the presence of a canonical tag.
Why it matters: Consistent canonical tags across the site prevent duplicate-content ambiguity at scale, not just on individual pages.
What it is: Flags URLs that run unusually long across the crawled site.
Why it matters: Very long URLs are harder to share, read, and remember, and can signal disorganized parameter- or ID-heavy URL structures.
What it is: Detects multiple crawled pages sharing the exact same `<title>` tag.
Why it matters: Duplicate titles make it harder for search engines to tell pages apart and for users to distinguish results in the SERP.
What it is: Detects multiple crawled pages sharing the exact same meta description.
Why it matters: Repeated descriptions waste an opportunity to differentiate each page’s snippet and improve click-through from search results.
What it is: Finds `<img>` sources across the crawl that return an error instead of an image.
Why it matters: Broken images look unpolished, hurt user trust, and waste the alt-text/accessibility value the image was meant to provide.
What it is: Reports that this specific page could not be retrieved at all during the audit.
Why it matters: If the audit can’t fetch a page, neither can a search engine crawler under similar conditions -- the page is effectively invisible.
Fix it: Broken Link CheckerWhat it is: Reports that the page responded with an HTTP status other than 200 OK.
Why it matters: Anything other than a clean 200 (or an intentional redirect) tells search engines something is wrong with that URL.
Fix it: Bulk HTTP Status Code CheckerWhat it is: Reports that the URL resolves to a non-HTML resource (PDF, image, JSON, etc.), which most on-page checks don’t apply to.
Why it matters: Running text/heading/meta checks against a non-HTML resource would produce meaningless results, so this flags it instead.
What it is: Checks that this individual crawled page, specifically, loads over HTTPS.
Why it matters: A site can have HTTPS configured at the domain level yet still leak individual pages over HTTP through old links or misconfiguration.
What it is: Checks that this specific page has a canonical tag, and that it points where it should.
Why it matters: A missing or mismatched canonical on even one important page can cause it to be indexed under the wrong URL.
What it is: Checks this page’s meta robots tag (and X-Robots-Tag header) for noindex/nofollow directives.
Why it matters: An accidental noindex on a single important page removes just that page from search results without affecting the rest of the site -- easy to miss.
Titles, headings, content quality, and the internal signals that tell search engines what a page is about.
Fix these with the On-Page Content toolsWhat it is: Checks that the page has a `<title>` tag at all.
Why it matters: The title tag is the single strongest on-page relevance signal and is almost always what search engines display as the clickable headline.
Fix it: Meta Tags GeneratorWhat it is: Checks the title length falls in the range that search engines typically display in full without truncating.
Why it matters: A title that gets cut off in search results loses its message and its call to click right at the moment it matters most.
Fix it: Meta Tags GeneratorWhat it is: Checks that this page’s title differs from titles on other pages of the site.
Why it matters: Identical titles across pages make it harder for search engines and users to tell which result actually answers their query.
What it is: Checks whether the page’s target keyword appears in the title tag.
Why it matters: Keyword presence in the title remains one of the clearest relevance signals search engines use to match queries to pages.
What it is: Checks that the page has a meta description tag.
Why it matters: A written description gives you control over the search-result snippet instead of leaving it to an auto-generated excerpt.
Fix it: Meta Tags GeneratorWhat it is: Checks the meta description length against the range search engines typically show without truncation.
Why it matters: An overly long description gets cut off mid-sentence in results, and a too-short one wastes space that could sell the click.
Fix it: Meta Tags GeneratorWhat it is: Checks whether the target keyword appears in the meta description.
Why it matters: Search engines bold matching query terms in the snippet, which draws the eye and reinforces relevance to the searcher.
What it is: Checks the URL is readable, hyphen-separated, and free of unnecessary IDs or parameter clutter.
Why it matters: Clean URLs are easier for users to read and trust, and give search engines an extra readable relevance signal.
What it is: Checks that the URL path isn’t excessively long.
Why it matters: Shorter, more direct URLs are easier to share, remember, and display in full within search results.
What it is: Checks whether the URL slug includes the page’s target keyword.
Why it matters: A keyword-aligned slug reinforces topical relevance and is visible in the search-result URL line itself.
What it is: Checks that the page uses exactly one H1 heading.
Why it matters: A single H1 gives both users and search engines one unambiguous statement of what the page is about; multiple H1s dilute that signal.
Fix it: Heading Tags SEO CheckerWhat it is: Checks whether the H1 heading includes the page’s target keyword.
Why it matters: The H1 is the first thing both users and crawlers read as the page’s main topic statement.
What it is: Checks that headings descend in logical order (H1 then H2 then H3) without skipping levels.
Why it matters: A broken hierarchy (H1 straight to H4, for example) confuses both screen readers and search engines trying to parse the page’s outline.
Fix it: Heading Tags SEO CheckerWhat it is: Checks overall heading usage for structural soundness across the page.
Why it matters: A well-structured heading outline helps search engines break the page into topics and helps users scan it quickly.
What it is: Checks that the target keyword appears in the body at a natural frequency -- present, but not stuffed.
Why it matters: Too little keyword usage weakens relevance signals; too much reads as keyword stuffing and risks a quality penalty.
Fix it: Keyword Density CheckerWhat it is: Checks whether the content uses the broader vocabulary and related terms a topic would naturally include.
Why it matters: Modern search engines judge topical depth by vocabulary breadth, not just exact-keyword repetition -- thin vocabulary reads as thin coverage.
What it is: Checks whether subheadings reflect the range of subtopics the content actually covers.
Why it matters: Subheadings that map to real subtopics make content easier to scan and easier for search engines to match to specific queries.
What it is: Measures the page’s body word count against what’s typical for genuinely comprehensive coverage of its topic.
Why it matters: Very thin pages rarely have room to satisfy search intent fully and tend to underperform pages that cover a topic in depth.
What it is: Flags pages whose content is too sparse to meaningfully satisfy a searcher’s intent.
Why it matters: Thin content is one of the most common reasons pages fail to rank at all, regardless of other optimization.
What it is: Uses near-duplicate content fingerprinting to detect pages that are substantially the same as another page on the site.
Why it matters: Duplicate pages compete with each other for the same rankings instead of each earning its own visibility.
What it is: Scores the text’s readability using the Flesch Reading Ease formula.
Why it matters: Content that’s needlessly hard to read loses readers before they get to the point, hurting engagement signals search engines can observe.
Fix it: Content Readability CheckerWhat it is: Checks the ratio of active-voice to passive-voice sentences in the body content.
Why it matters: Active voice is generally more direct and readable, which supports both user engagement and clarity for AI systems parsing the content.
What it is: Checks average sentence length against readable norms.
Why it matters: Long, dense sentences are harder to skim and to parse into a clean answer, both for readers and for AI summarization.
Fix it: Content Readability CheckerWhat it is: Checks paragraph length against readable, scannable norms.
Why it matters: Wall-of-text paragraphs discourage reading on screens; shorter paragraphs improve scannability and time-on-page.
What it is: Checks usage of transition words and phrases that connect ideas between sentences.
Why it matters: Transitions make content flow logically, which readability scoring tools and real readers both reward.
What it is: Checks whether tabular data is marked up as real `<table>` elements where appropriate.
Why it matters: Real tables are more accessible and more likely to be lifted into rich results or AI answers than data described only in prose.
What it is: Checks usage of `<ul>`/`<ol>` list markup for list-like content.
Why it matters: Proper list markup is easier to scan, more accessible, and more extractable for featured snippets and AI answers than a comma-separated paragraph.
What it is: Checks whether the page includes a clear FAQ-style question-and-answer section.
Why it matters: FAQ sections directly match how people phrase search queries and are prime material for featured snippets and AI-generated answers.
What it is: Checks for a table of contents on longer content pages.
Why it matters: A TOC helps readers jump to what they need and can generate jump-link sitelinks in search results.
What it is: Checks that images have descriptive alt text rather than empty or missing attributes.
Why it matters: Alt text is essential for screen-reader accessibility and is the primary signal search engines use to understand and rank images.
Fix it: Image SEO AnalyzerWhat it is: Checks whether image filenames are descriptive rather than generic camera/CMS-generated strings.
Why it matters: A descriptive filename like `red-running-shoes.jpg` gives search engines context that `IMG_4021.jpg` never can.
What it is: Checks that `<img>` tags declare explicit width and height attributes.
Why it matters: Without declared dimensions, the browser can’t reserve space for the image, causing layout shift as it loads -- a direct Core Web Vitals hit.
What it is: Checks whether below-the-fold images use `loading="lazy"`.
Why it matters: Lazy loading defers offscreen images so the browser isn’t competing to download them before the visible content is ready.
What it is: Checks whether images use modern formats (WebP/AVIF) instead of only legacy JPEG/PNG.
Why it matters: Next-gen formats deliver the same visual quality at meaningfully smaller file sizes, speeding up page load.
Fix it: Image SEO AnalyzerWhat it is: Measures how many internal links point to this page from elsewhere on the site.
Why it matters: Pages with more internal inbound links are crawled more often and treated as more important by search engines.
What it is: Checks whether internal links use varied, descriptive anchor text rather than repeating the same generic phrase.
Why it matters: Descriptive anchor text tells both users and search engines what the linked page is about before they click.
What it is: Checks that internal links on this page resolve successfully rather than 404ing.
Why it matters: Broken internal links waste crawl budget, break the user journey, and leak the link equity that was meant to flow to the target.
Fix it: Broken Link CheckerWhat it is: Checks whether the page links out to relevant, reputable external sources.
Why it matters: Citing credible sources supports E-E-A-T and gives readers (and AI systems) a way to verify claims.
What it is: Checks that external links on the page resolve successfully rather than pointing to dead pages.
Why it matters: Dead outbound links look neglected and erode trust, even though they don’t directly affect crawl budget the way internal ones do.
What it is: Checks that a `Link: rel=canonical` header or tag is properly formed for this page.
Why it matters: A well-formed canonical is the clearest way to tell search engines exactly which URL should be indexed.
What it is: Checks that the canonical URL actually resolves and points to a real, accessible page.
Why it matters: A canonical pointing to a broken or redirecting URL gives search engines a dead end instead of a clear signal.
What it is: On-page check for a declared `lang` attribute on the document.
Why it matters: Declaring language helps search engines match the page to the right language’s search results and helps assistive technology pronounce it correctly.
What it is: Checks whether the page credits a visible author with identifiable expertise.
Why it matters: Google’s quality guidelines explicitly weigh author expertise as part of E-E-A-T, especially for YMYL (health/finance/legal) content.
What it is: Checks whether the page declares a clear publication date.
Why it matters: A visible date helps users and search engines judge whether the content is current, especially for time-sensitive topics.
What it is: Checks whether the page shows a last-updated/modified date, and how recent it is.
Why it matters: Freshness signals matter more for some queries than others, but a visibly stale update date can quietly undercut trust either way.
What it is: Checks for a visible breadcrumb trail in the page UI (independent of the BreadcrumbList schema check).
Why it matters: Breadcrumbs help users understand where they are in the site and provide an easy path back to parent categories.
Fix it: Breadcrumb Schema GeneratorWhat it is: Checks that the page includes at least some relevant structured data for its content type.
Why it matters: Structured data is the clearest way to hand search engines and AI systems an unambiguous description of the page’s content.
Fix it: Schema Markup GeneratorWhat it is: Checks that the homepage exposes a real navigation menu with crawlable links.
Why it matters: The homepage’s nav menu is usually the single biggest source of internal links pointing deeper into the site.
What it is: For utility/tool-type pages, checks that the actual interactive input fields are present in the markup.
Why it matters: A tool page with no detectable inputs may be rendering its functional UI in a way crawlers -- and some users -- can’t see.
What it is: For blog/article pages, checks for a table of contents aiding navigation through longer posts.
Why it matters: Long-form posts benefit disproportionately from a TOC, both for reader navigation and for search engines’ jump-link sitelinks.
Open Graph and Twitter Card markup controlling how links preview when shared.
Fix these with the Structured Data toolsWhat it is: Checks for Open Graph tags (og:title, og:description, og:image, etc.) controlling how the page previews when shared.
Why it matters: Without Open Graph tags, social platforms fall back to guessing a title/image, often producing an ugly or irrelevant preview.
Fix it: Open Graph TesterWhat it is: Checks for Twitter/X Card meta tags controlling the link preview format on that platform.
Why it matters: X renders link previews from its own Card tags, not Open Graph alone, so this needs separate coverage.
Fix it: Open Graph TesterWhat it is: Checks for general social-sharing affordances (share buttons, complete social metadata) on the page.
Why it matters: Easy sharing paired with a strong preview increases the odds content actually gets shared once someone wants to.
What it is: Samples multiple crawled pages to check how consistently Open Graph tags are implemented across the whole site.
Why it matters: A site that gets OG tags right on the homepage but misses them elsewhere still produces broken previews on most shared links.
Fix it: Open Graph TesterWhat it is: Samples multiple crawled pages to check how consistently Twitter Card tags are implemented across the whole site.
Why it matters: Consistent Card coverage matters more than a single well-optimized page if most of the site’s content gets shared on X.
Experience, Expertise, Authoritativeness, and Trust signals search engines weigh for quality raters and ranking.
Fix these with the AI Search toolsWhat it is: Checks for the presence of foundational trust pages sitewide -- About, Contact, Privacy Policy, and similar.
Why it matters: These pages are a baseline trust signal Google’s quality raters explicitly look for, especially for sites making claims that affect a reader’s money or wellbeing.
Fix it: E-E-A-T CheckerWhat it is: Checks whether this specific page visibly credits an author.
Why it matters: Attributed content signals accountability and expertise, both core components of E-E-A-T.
Fix it: E-E-A-T CheckerWhat it is: Checks whether this specific page visibly shows a publication date.
Why it matters: A visible date lets readers judge whether advice or claims on the page are still current.
How pages connect to each other -- the paths crawlers and visitors use to discover content.
Fix these with the Technical SEO toolsWhat it is: Flags pages the crawl reached (e.g. via sitemap) but that no other crawled page links to internally.
Why it matters: A page with zero internal links pointing to it is hard for both crawlers and users to discover, no matter how good the content is.
Fix it: Orphan Page CheckerWhat it is: Flags pages that receive very few internal links relative to the rest of the site.
Why it matters: Thin internal linking starves a page of both crawl attention and the topical context that links between related pages provide.
What it is: Lists internal links discovered during the crawl that point to pages returning an error status.
Why it matters: Broken internal links interrupt the user journey and burn crawl budget on dead ends instead of real content.
Fix it: Broken Link CheckerWhat it is: Checks whether internal link anchor text is descriptive and varied rather than repeated generic phrases like "click here."
Why it matters: Generic anchor text ("click here", "read more") tells search engines nothing about what the linked page covers.
What it is: Counts how many internal pages the homepage links to.
Why it matters: The homepage usually holds the most authority on a site; how widely it distributes internal links shapes how that authority spreads.
What it is: Checks the links found specifically on this page for ones that resolve to an error.
Why it matters: A page with several broken links reflects poorly on content freshness and directly interrupts navigation for anyone who clicks one.
Fix it: Broken Link CheckerStructured data (JSON-LD) that lets search engines and AI systems parse a page’s meaning directly.
Fix these with the Structured Data toolsWhat it is: Detects JSON-LD structured data blocks that fail to parse as valid JSON.
Why it matters: A single syntax error can invalidate an entire schema block, silently forfeiting whatever rich-result eligibility it was meant to unlock.
Fix it: Schema Markup GeneratorWhat it is: Lists which schema.org types (Article, Product, FAQPage, etc.) were found in the page’s structured data.
Why it matters: Knowing exactly what schema is already present makes it easy to spot what’s missing for this content type.
Fix it: Schema Markup GeneratorWhat it is: Suggests specific schema types this page is likely missing, based on its detected content type.
Why it matters: Adding the right schema type is often the single fastest way to become eligible for a new rich-result feature.
Fix it: Schema Markup GeneratorContent depth, readability, and structural signals search engines use to judge topical authority.
Fix these with the On-Page Content toolsWhat it is: Scores overall content comprehensiveness into a thin/moderate/optimal tier based on depth of coverage.
Why it matters: Search engines increasingly reward pages that cover a topic comprehensively over pages that touch it only briefly.
Fix it: Semantic Content Analysis ToolWhat it is: Evaluates whether sentence complexity is holding back the content’s overall readability.
Why it matters: Content that’s unnecessarily hard to parse loses both human readers and the AI systems trying to summarize it accurately.
What it is: Evaluates whether the page’s subheadings form a clear, logical hierarchy of topics and subtopics.
Why it matters: A clear hierarchy helps search engines segment the page into topically distinct, individually rankable sections.
What it is: Checks whether list-like or tabular information is actually marked up as lists/tables rather than left as plain prose.
Why it matters: Structured formatting is both easier to scan for humans and easier to extract cleanly for featured snippets and AI answers.
What it is: Scores how completely the page’s body content actually covers its stated target keyword phrase.
Why it matters: A page optimized in the title and headings but missing the keyword from the body sends a weaker, inconsistent relevance signal.
What it is: Checks whether the URL structure groups related content into topical directories (a "silo") rather than a flat structure.
Why it matters: Siloed URL structures reinforce topical relationships for search engines and make site sections easier for users to navigate.
Fix it: SEO Silo Structure CheckerWhat it is: Aggregates semantic structural quality (headings, content depth, formatting) across the crawled site.
Why it matters: A sitewide view catches structural problems -- like most pages lacking proper headings -- that per-page checks alone can miss.
Fix it: Semantic Content Analysis ToolWhat it is: Flags pages that appear to render most of their content via client-side JavaScript rather than server-delivered HTML.
Why it matters: The crawler -- like many real crawlers -- can’t execute JavaScript, so heavily CSR pages risk being seen as near-empty by search engines that don’t render them either.
What it is: Checks whether this individual page sits within a logical category path rather than a flat, unstructured URL.
Why it matters: A page’s URL path is itself a signal of where it fits in the site’s topical hierarchy.
Fix it: SEO Silo Structure CheckerWhat it is: Checks use of semantic HTML5 elements (`<article>`, `<nav>`, `<main>`, `<aside>`, etc.) instead of generic `<div>` soup.
Why it matters: Semantic tags give both browsers and search engines a built-in outline of the page’s structure without extra markup.
Fix it: Semantic Content Analysis ToolAnswer Engine and Generative Engine Optimization -- structuring content so AI assistants and answer engines can extract and cite it.
Fix these with the AI Search toolsWhat it is: Checks for FAQPage structured data marking up question-and-answer content.
Why it matters: FAQ schema is one of the most direct ways to feed exact question/answer pairs to AI answer engines and traditional rich results alike.
Fix it: Schema Markup GeneratorWhat it is: Checks for Article/NewsArticle/BlogPosting structured data.
Why it matters: Article schema gives search and AI systems clean metadata -- headline, author, date -- for editorial content.
Fix it: Schema Markup GeneratorWhat it is: Checks for Organization structured data describing the publishing entity.
Why it matters: Organization schema helps establish who is actually behind the content, feeding both knowledge panels and AI trust assessments.
What it is: Checks for structured data explicitly identifying the content’s author.
Why it matters: Machine-readable authorship is a concrete E-E-A-T signal AI systems can parse without having to infer it from prose.
What it is: Checks for Person structured data describing an individual referenced on the page.
Why it matters: Person schema disambiguates named individuals for search and AI systems, useful for author bios, team pages, and expert quotes.
What it is: Checks for BreadcrumbList structured data (the AEO-focused counterpart of the technical breadcrumb check).
Why it matters: Breadcrumb schema gives AI systems a clean signal of how this page fits into the site’s broader topic hierarchy.
Fix it: Breadcrumb Schema GeneratorWhat it is: Checks for base WebPage structured data describing the page itself.
Why it matters: WebPage schema is a foundational entity that other, more specific schema types (Article, Product, etc.) build on top of.
What it is: Checks for HowTo structured data on step-by-step instructional content.
Why it matters: HowTo schema lets AI systems and rich results present your steps directly, which is exactly the format many how-to queries want.
What it is: Checks for Product structured data, where the page is describing a purchasable item.
Why it matters: Product schema feeds price, availability, and rating data directly into shopping-oriented search and AI experiences.
What it is: Checks for Review or AggregateRating structured data.
Why it matters: Review schema is what makes star ratings appear directly in search results and is heavily weighed in AI purchase-recommendation answers.
What it is: Checks for Speakable structured data marking sections suited for text-to-speech readout.
Why it matters: Speakable schema helps voice assistants identify exactly which part of the page is safe and appropriate to read aloud.
What it is: Checks whether the content references clear, named entities (people, places, organizations, products) rather than vague generalities.
Why it matters: AI systems reason in terms of entities and their relationships; content with weak entity presence is harder for them to place and cite.
What it is: Checks that entities are referred to consistently by name throughout the page rather than inconsistently across sections.
Why it matters: Consistent naming helps AI systems confidently link every mention back to the same real-world entity.
What it is: Evaluates whether the page addresses the full range of subtopics a comprehensive answer on this subject would cover.
Why it matters: AI answer engines favor sources that cover a topic completely enough to be cited as a single authoritative answer.
What it is: Checks how many headings are phrased as actual questions rather than statements.
Why it matters: Question-phrased headings map directly to how people phrase queries to search engines and AI assistants alike.
What it is: Checks whether questions posed in headings are followed immediately by a direct, extractable answer.
Why it matters: AI answer engines and featured snippets both favor a concise direct answer immediately after the question, not one buried paragraphs later.
What it is: Checks for clear, isolated definitions of key terms ("X is...") the content introduces.
Why it matters: A clean definition block is exactly the shape of content AI systems most reliably extract for "what is X" queries.
What it is: Checks for clearly sequenced, numbered instructional steps.
Why it matters: Sequential steps are easy for AI systems to extract and present as a structured how-to answer.
What it is: Checks for tables comparing multiple options, products, or approaches.
Why it matters: Comparison content is exactly what AI shopping and decision-support answers are built to extract and summarize.
What it is: Checks for an explicit pros-and-cons breakdown.
Why it matters: A clear pros/cons list is a compact, highly extractable format for AI systems answering comparison or decision questions.
What it is: Checks whether the content includes concrete statistics and factual data points, not just general claims.
Why it matters: Specific, citable numbers are more likely to be pulled into AI-generated answers than vague qualitative statements.
What it is: Checks for clear, self-contained statements an AI system could quote and attribute directly.
Why it matters: Content written in citable, standalone statements is easier for generative engines to lift and credit as a source.
What it is: Checks for visible links to About, Contact, and policy pages establishing who is behind the content.
Why it matters: AI systems weigh publisher trustworthiness when deciding which sources to cite, and these pages are a baseline signal of a real organization.
What it is: Checks whether the author’s credentials or relevant expertise are visibly stated, not just their name.
Why it matters: Demonstrated expertise (not just attribution) is what actually strengthens an E-E-A-T and AEO trust signal.
Fix it: E-E-A-T CheckerWhat it is: Evaluates whether the content reflects current information rather than stale or outdated facts.
Why it matters: AI systems and search engines both discount content that reads as out of date on fast-moving topics.
What it is: Checks for a visible last-updated date distinct from the original publish date.
Why it matters: An update timestamp signals the content is actively maintained, which matters more for AI trust scoring than a publish date alone.
What it is: Checks whether claims are backed by cited sources or references.
Why it matters: Cited sources let AI systems verify claims and are a direct component of how they assess content credibility.
What it is: Checks for signs of original analysis, data, or perspective rather than content that only restates common knowledge.
Why it matters: AI systems and search engines increasingly favor sources offering something genuinely new over rehashed summaries.
What it is: Checks for original visual assets (custom charts, screenshots, diagrams) rather than only stock imagery.
Why it matters: Original visuals are both harder to find elsewhere and a concrete signal of first-hand effort behind the content.
What it is: Evaluates overall organization -- logical flow from introduction through to conclusion.
Why it matters: A clearly organized page is easier for both readers and AI extraction systems to follow and summarize accurately.
What it is: Checks for concise, self-contained answer snippets in the ideal length range for featured snippets and voice answers.
Why it matters: This word count matches the typical length search engines and assistants read aloud or display as a direct answer.
What it is: Checks how tightly this page’s content relates to the broader topic cluster it belongs to on the site.
Why it matters: Content that stays tightly on-topic within a cluster reinforces the site’s overall topical authority for AI and search alike.
What it is: Aggregates the presence of Experience, Expertise, Authoritativeness, and Trust signals across the page.
Why it matters: E-E-A-T is explicitly part of Google’s quality rater guidelines and increasingly factors into how AI systems select sources to trust.
What it is: Checks whether the brand or organization is clearly named on the page itself.
Why it matters: AI systems attribute claims to a source; a page that never names the brand behind it is harder to credit or trust.
What it is: Checks whether the page clearly states what makes its offering or perspective distinct.
Why it matters: A clear value proposition helps both users and AI systems understand why this source, specifically, is worth citing or choosing.
What it is: Checks whether content is broken into clearly delimited, self-contained chunks rather than one continuous block.
Why it matters: AI systems retrieve and cite content in chunks; well-chunked content is more likely to be extracted cleanly and accurately.
What it is: Checks that tabular data uses real, properly structured `<table>` markup an AI system can parse programmatically.
Why it matters: A table rendered as styled `<div>`s or an image can’t be reliably parsed by AI systems the way a real HTML table can.
Fix it: AI Content DetectorWhat it is: Checks that the writing reads naturally rather than as mechanically keyword-optimized text.
Why it matters: Both search quality systems and AI models are tuned to recognize and discount unnatural, keyword-stuffed writing.
What it is: Checks whether technical or specialized terms are briefly explained when first introduced.
Why it matters: Unexplained jargon makes content harder for a general audience -- and for AI systems generating answers for non-experts -- to use confidently.
What it is: Checks whether the page leads with a direct answer before diving into supporting detail.
Why it matters: Answer-first structure matches how AI systems prefer to extract a concise response before optionally including context.
What it is: Checks whether the page addresses the different intents a searcher on this topic might have (informational, comparative, transactional).
Why it matters: A single query can trigger different underlying intents; covering more of them widens the range of questions the page can answer.
What it is: Checks whether the content makes the relationships between named entities explicit rather than implied.
Why it matters: Explicit relationships ("X, the founder of Y") are far easier for AI knowledge extraction than context the reader has to infer.
What it is: Checks that the same concept is referred to with consistent terminology throughout, rather than switching synonyms.
Why it matters: Inconsistent terminology can make AI systems treat the same concept as multiple different things.
What it is: Checks whether existing structured data blocks are filled out completely rather than missing common optional fields.
Why it matters: A sparse schema block is valid but under-informative; filling recommended fields gives AI and search systems more to work with.
What it is: Checks overall formatting -- headings, chunking, structure -- for how easily a language model could parse the page.
Why it matters: Content that’s naturally easy for an LLM to parse is more likely to be retrieved, summarized, and cited accurately.
What it is: Evaluates how easily a reader (or an extraction system) can scan the page and locate specific information quickly.
Why it matters: Scannable content, with clear headings and formatting, serves both time-pressed human readers and automated extraction equally well.
What it is: Checks whether robots.txt explicitly allows or blocks known AI crawlers (GPTBot, Google-Extended, and similar).
Why it matters: If AI crawlers are blocked, the site can’t appear in AI-generated answers at all, regardless of how well-optimized the content is.
Fix it: Robots.txt GeneratorWhat it is: Checks for an llms.txt file at the domain root -- an emerging convention giving AI agents a concise, curated guide to the site.
Why it matters: llms.txt is a direct, purpose-built channel for telling AI agents what your site is and which pages matter most, ahead of them inferring it from a crawl.
Fix it: LLMs.txt Generator