Technical Audit FAQ
Frequently asked questions about Technical Audit in OnPagePilot.
Fifteen check families: crawlability and indexing, response codes and server issues, URL structure and redirects, content and metadata, images and media, internal linking, pagination and navigation, structured data and schema, social media and Open Graph, HTTPS and security, international SEO, JavaScript and rendering, mobile and performance, accessibility and usability, and analytics and 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.
Still deciding on Technical Audit?
Ask us the question this page did not answer, or compare the plans that include Technical Audit.