Technical Audit FAQ

Frequently asked questions about Technical Audit in OnPagePilot.

Technical Audit

Seventeen check families: 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.

Because the fix for a broken canonical is different on Shopify than on WordPress. The audit identifies the platform, the SEO plugin and the e-commerce layer - each with a confidence score - and every fix suggestion that follows is written for that stack.

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 and Rank Math SEO plugins. The audit checks themselves do not depend on the platform; a site on any other stack is audited in full, and the fix suggestions are then written from the issue details alone, without a platform line.

It is written by the AI from the details of that specific issue, for the detected platform - something you can hand straight to a developer or apply yourself. Not a generic "improve your meta descriptions".

Yes. The full report exports as PDF or CSV, and any single issue exports as JSON for a ticket.

Ready To Transform Your SEO Strategy?

Pick a plan and put all five features to work on your own domain — search rankings and AI visibility, measured in one place.