SiteFix.app
/
Start an audit
SCAN. ANALYZE. FIX.

A technical SEO audit you can act on

Find what a public page actually returns. See the evidence, the affected URLs, and a practical way to verify each repair.

What the audit checks

SiteFix.app discovers pages from your starting URL, on-site links, and XML sitemaps. It reads up to 25 public HTML pages within a request and time budget. The report shows which pages were read, skipped, blocked, or left unconfirmed.

  • Page titles, descriptions, main headings, and heading order.
  • Canonical declarations, noindex directives, snippet restrictions, and search crawl rules.
  • Image text alternatives, observed broken internal links, and repeated titles, descriptions, or content.
  • Parseable schema declarations, context, and basic brand or product details.

Evidence before a score

Each issue includes its rule, page evidence, affected URLs, recommendation, and expected verification result. Unknown and not-applicable checks are excluded from the score. A link that was not fetched is not marked healthy. A page that disappears from the next crawl is not automatically marked fixed.

Check the browser separately

After a successful audit, you can open the entry page at phone and desktop sizes. The browser records content appearance, layout shifts, horizontal overflow, and a first-screen screenshot. This is a single remote run without simulated phone hardware or a full interaction test. It does not supply real-user INP or long-term Core Web Vitals.

What it cannot establish

A successful fetch does not prove Google indexed the page. A canonical tag does not prove Google selected that canonical. The basic crawler does not run page scripts or enter authenticated areas. Confirm indexing and search performance in the website owner’s tools.

Turn the findings into a change

Choose one or more issues, generate a task for your coding assistant, and apply the changes in your own repository. Then deploy the reviewed change and use Recheck after fixes on the same entry URL.

Make the next fix a clear one.

Start with public-page evidence. Let your coding assistant find the right files, then verify the change.

Run a website audit