Technical Audit

What a technical audit is for

Content earns authority; technical faults lose it. A page that cannot be crawled, returns the wrong response code, renders its main content only in JavaScript the crawler never runs, or fails Core Web Vitals on mobile does not get the ranking the writing deserves. A technical audit finds those faults before the search engine does.

The OnPagePilot Technical Audit is built to answer two questions per issue: what exactly is wrong, on which URLs, and what change fixes it on the platform this site actually runs.

It detects your stack first

Before it judges anything, the audit identifies what the site runs: WordPress (and WooCommerce), Shopify, Magento, BigCommerce, PrestaShop, OpenCart, Squarespace, Wix, Webflow, Drupal, Joomla, TYPO3, Ghost, HubSpot CMS, Umbraco, Sitecore, Kentico and Craft CMS, plus the Yoast or Rank Math SEO plugin and the e-commerce layer, each with a confidence score.

Everything that follows is written for that stack. A missing alt text on a WordPress site and the same issue on a custom ASP.NET site are the same finding with two different fixes, and the audit knows which one you need.

What it checks

Seventeen check families cover the whole technical surface of a site: crawlability, response codes, robots and sitemaps, URL structure, titles, meta descriptions, headings and content, images and media, internal linking, pagination and navigation, structured data, social and Open Graph, HTTPS and SSL, international SEO and hreflang, JavaScript rendering, mobile performance and Core Web Vitals, accessibility, and analytics tracking.

The overview shows a site health score with error, warning and passed counts, so the first look tells you how much work there is and where it sits.

Fixes, not lectures

For each issue the AI writes a fix suggestion from the details of that issue, tailored to the detected platform. It is meant to be handed straight to a developer: the markup change, and where the platform needs it, the data change behind it. There is no generic advice to improve your meta descriptions.

The issue details list the exact URLs, what is wrong on each, and the fix, readable as lines or as JSON.

Choose what the audit looks at

Audit profiles decide which checks run. Start with one of the three system templates, or clone one and choose the checks yourself. A profile that matches the site keeps the report focused: a static marketing site does not need e-commerce checks, and a shop does not need to be told about a missing blog sitemap.

A practical workflow

1. Run the audit on the whole site with a system profile. Read the health score and the error count before anything else.

2. Fix errors before warnings. Response codes, crawlability and robots come first: a page the crawler cannot reach has no other issues that matter.

3. Hand each fix to the person who can ship it. Export the issue as JSON for a ticket, or the whole report as PDF or CSV for a review.

4. Re-run after the fixes land. The report keeps a six-week site health trend and an issue breakdown by category, so you can see the score move and catch regressions.

Take it with you

Export the full report as PDF or CSV, or export the details of a single issue as JSON for a ticket. The audit sits beside the rest of OnPagePilot: the Topical Authority map tells you which pages to build, and the audit confirms the pages you built are crawlable and clean, so the authority you earn is not lost to a technical fault.

Where to go next

The Technical Audit feature page shows stack detection, the overview, issue details and export with product captures. The Technical Audit FAQ answers the questions we get most often about what is checked and how fixes are generated.

If you are in the BETA and an audit reports something that does not match your site, tell us on the contact page. Every report we look at together makes the next one better.