Run a Next.js SEO audit with your coding assistant

Connect the assistant and choose one deployed site

The dotmap connection page provides setup for Claude Code, Cursor and VS Code. Use its current setup instructions, authenticate in your browser, and select a public deployment that you are authorized to audit. The dotmap crawler cannot inspect localhost or a private preview.

For Claude Code, the connection command below registers dotmap's remote MCP server. Cursor and VS Code use their own configuration flows on the connection page. Connecting the tool does not deploy code changes; review the resulting diff as part of your normal development workflow.

claude mcp add --transport http dotmap https://dotmap.ai/mcp

1. 01Connect and authenticate using the instructions for your assistant on /connect.
2. 02Ask: Audit my public deployment and list the weakest indexable pages, with their specific issues.
3. 03Choose one issue shared by a route or template. Ask for a proposed fix and its affected URLs before editing.

Map the finding to the Next.js implementation

For the App Router, inspect the route's metadata export or generateMetadata function, its layouts, and the robots and sitemap conventions. Read the documentation for the installed Next.js version: API details and caching behavior can change. Avoid fixing the same missing canonical by declaring conflicting values in both a parent layout and a child page.

The example below gives a public product route its own title, description and canonical. The absolute origin must come from your deployment's metadataBase or an explicit absolute canonical. It is an implementation example, not a measured ranking improvement.

import type { Metadata } from "next";

export const metadata: Metadata = {
  title: "Website SEO audits and monitoring",
  description: "Check public pages for crawl, metadata and content issues.",
  alternates: { canonical: "https://example.com/product" },
};

Verify the fix after deployment

Run the checks required by the repository, review the diff, and deploy through its normal release process. Fetch the actual public URL and check the response status, metadata and visible content. Inspect a second page using the same template to catch regressions beyond the original finding.

Re-audit the deployed site with the same scope. Compare the affected URLs,
not just the average score. Report the deployed canonical, indexing directive
and remaining issues. Do not claim a Google ranking or indexing improvement
from the audit score alone.

Measure whether the work helped people find the product

Check the individual URL in Search Console after Google recrawls it. Use the crawl date to distinguish an old observation from the current response. Then compare the same query-page pairs over comparable periods, separating brand searches and irrelevant report URLs from searches by prospective customers.

Track audit starts, completed audits and signups alongside organic clicks. A better score is useful diagnostic evidence, but a claim about acquisition needs visitor and conversion measurements. Record the deployment date and keep concurrent changes in mind before attributing a traffic difference to a single fix.