Page is set to noindex
https://www.harbour-bakery.example/wholesale- Indexability
indexable→not indexable
CorrectionRemove the noindex directive if this page should rank. Intentional on staging, thank-you, and filter pages — verify before changing.
Example report. The studio, the website and every figure are invented. It is rendered by the same components as a real client link, from two fixed audits run through the same comparison.
Example · invented website, studio and figures · nothing here was verified
Questions about this report? hello@studio.example
Comparing the audit of with the audit of . Traffic figures cover the seven complete Pacific days ending at the earlier one, so a page that has since lost its traffic is still ranked by what it was carrying.
These rules were not firing at the earlier audit and are firing now. The change happened somewhere between the two audit times.
CorrectionRemove the noindex directive if this page should rank. Intentional on staging, thank-you, and filter pages — verify before changing.
CorrectionAdd a unique <title>. It is the strongest on-page relevance signal and the clickable line in the search result.
These were findings at the earlier audit. The later audit fetched the same page, got an auditable response, and the rule no longer fired.
CorrectionUpdate or remove the links. Broken internal links waste crawl budget and are a direct dead end for visitors.
CorrectionWrite one. Google often rewrites it, but when it does use yours it directly drives click-through rate.
CorrectionAdd alt text describing the image, or alt="" if it is purely decorative. A missing attribute and an empty one mean different things.
CorrectionSet width and height so the browser can reserve space. This is the most common single cause of a failing CLS score.
These stopped firing, but the later response cannot prove a fix — the page was not auditable, it no longer asks to be indexed, or crawl coverage changed underneath the rule. They are not counted as fixed.
CorrectionAim for 70-160 characters.
Tags that have a different value than at the earlier audit. Nothing here is a fault; it is here so an unexpected edit is visible.
Findings present at both audits. Nothing about them changed this period.
CorrectionAdd alt text describing the image, or alt="" if it is purely decorative. A missing attribute and an empty one mean different things.
CorrectionUnder ~300 words rarely satisfies an informational query. Either expand it or consolidate it into a stronger page.
CorrectionAdd og:title, og:description and og:image so shared links render a card instead of a bare URL.
CorrectionAim for 70-160 characters.
CorrectionAdd JSON-LD appropriate to the page type (Article, Product, FAQPage). It is what makes rich results eligible.
Findings come from comparing the two most recent completed audits of this site. The change was observed between the two audit times; its actual date and its author are unknown. Importance is measured over the 7 complete Pacific calendar days ending at the earlier audit — before the change — so a page that has already lost its traffic is still ranked by what it was carrying. Organic clicks and their share come from your imported Search Console rows. Search Console can omit rows, so a share is a share of what was imported, not of all Google traffic. Page visitors and their share come from your own tracker and cover every source, not search alone. Corrections are the published fix for the rule that fired. They are the general remedy for that rule, not an inspection of your code. A fix is only reported as verified when a later audit fetched the same page, got an auditable response, and the rule no longer fired.
Findings come from comparing the two most recent completed audits of this site. The change was observed between the two audit times; its actual date and its author are unknown. Importance is measured over the 7 complete Pacific calendar days ending at the earlier audit — before the change — so a page that has already lost its traffic is still ranked by what it was carrying. Organic clicks and their share come from your imported Search Console rows. Search Console can omit rows, so a share is a share of what was imported, not of all Google traffic. Page visitors and their share come from your own tracker and cover every source, not search alone. Corrections are the published fix for the rule that fired. They are the general remedy for that rule, not an inspection of your code. A fix is only reported as verified when a later audit fetched the same page, got an auditable response, and the rule no longer fired.