--- title: "SEO page audit | SEO Skill" description: "Audit one URL for technical SEO, metadata, canonicals, schema, links and Search Console queries. See the live evidence before changing the page." canonical: "https://seoskill.dev/docs/reports/audit-page" language: "en" --- # SEO page audit Inspect one live URL before changing its content or technical setup. The audit keeps crawl evidence and returned Search Console queries together so you can see what the page actually needs. ## Install and run the audit Install the CLI once, then run `seo start` to connect your site and Google data. After setup you can run this audit yourself or ask your agent to run it. Install the SEO CLI globally. ``` npm i -g seo ``` Run setup after installation. ``` seo start ``` Inspect one live page before changing it. ``` seo audit-page --url https://example.com/page ``` ## What you get from this audit Audit one URL for technical SEO, metadata, canonicals, schema, links and Search Console queries. See the live evidence before changing the page. Best for A search result, release, redirect, canonical, structured data, or content question points to one URL. Needs Live page fetch and extraction You get Audit one URL for technical SEO, metadata, canonicals, schema, links and Search Console queries. See the live evidence before changing the page. Use next Sitemap health check and technical site crawl Every report follows the same rules for missing data and outside estimates.[See how report data works](https://seoskill.dev/docs/reports#how-report-data-works). ## What you need before you run it The report uses the information below. Optional sources are only used when you ask for them. ### Live page fetch and extraction Provides redirects, response, metadata, headings, links, directives, structured data, and page text. ### Optional exact-URL Search Console context Adds returned query and performance evidence when the URL belongs to the selected property. ## Use a different report for these jobs These jobs need a different report or a manual review. [ ### You need to discover the same technical problem across a whole site rather than inspect one known URL. Run a site crawl. It follows eligible links and sitemaps within explicit limits, groups repeated findings, and saves a reusable site-level baseline. Sitemap health check and technical site crawl ](https://seoskill.dev/docs/reports/site-crawl)[ ### The page is technically sound and you need a Search Console-backed brief for improving its existing content. Run content optimization. It joins the live page with its returned queries and separates technical conflicts from supported content review ideas. Content optimization report ](https://seoskill.dev/docs/reports/content-optimization) ## Use the audit with an agent or in code The command above is enough for most work. These options let an agent, script or application run the same audit with explicit input and structured output. ### CLI Use the report catalog when an agent, script or CI job needs predictable JSON instead of the normal terminal output. Check the current input first, then run the audit with the validated parameters. Check the current input before the agent or script runs the audit. ``` seo reports describe audit-page --json ``` Once the input is valid, run the audit through the report catalog. ``` seo reports run audit-page --params '{"url":"https://example.com/product","site":"sc-domain:example.com","refresh":true}' --json ``` ### MCP An MCP agent follows the same two-step flow. It inspects the current schema, fills the required fields and only then runs the audit. Ask the MCP server for the current audit input. ``` { "id": "audit-page" } ``` Run the audit after the agent has checked and filled the input. ``` { "id": "audit-page", "params": { "url": "https://example.com/product", "site": "sc-domain:example.com", "refresh": true } } ``` ### TypeScript Install the package in a Node 22 project when your application needs to run the audit directly. The result includes the same evidence, warnings and limits returned through the CLI and MCP server. Add the SEO package to your project. ``` npm install seo ``` Run the audit from your TypeScript application. ``` import { executeReport } from 'seo/mcp' const result = await executeReport( 'audit-page', { "url": "https://example.com/product", "site": "sc-domain:example.com", "refresh": true }, ) console.log(result) ``` ## What to do next Choose the finding that affects this page's actual purpose, make one supported change and audit the URL again. A fresh page check is more useful than carrying an old crawl observation into the next decision. 1. 01Fix concrete contradictions and refetch the URL. 2. 02Run a site crawl when the same pattern may affect a template. ## Related reports [ Check sitemap URL status, redirects and access first. Run the full technical SEO crawl only when you need page content, links, metadata and affected URLs. Sitemap health check and technical site crawl ](https://seoskill.dev/docs/reports/site-crawl)[ Follow every redirect hop from one URL to its final page and check status codes, loops, chains, canonicals and link safety before updating links. Redirect trace ](https://seoskill.dev/docs/reports/redirect-trace)[ Build a content brief from one page, its Search Console queries and the headings or topics already present. Keep every suggestion tied to demand. Content optimization report ](https://seoskill.dev/docs/reports/content-optimization) ## Sources used by this audit These primary sources define the provider data or search controls used by the result. - [Google canonical URL guidance](https://developers.google.com/search/docs/crawling-indexing/consolidate-duplicate-urls) - [Google robots meta and snippet controls](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag) - [Google structured data guidance](https://developers.google.com/search/docs/appearance/structured-data/intro-structured-data) - [Google JavaScript SEO guidance](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics)