SEO

Audit titles and meta descriptions

Compare the title and meta description of each top page against the queries it actually ranks for in Search Console, and find missing, duplicate, truncated or misaligned metadata on the pages where a rewrite would earn the most clicks.

  • Audit our page titles and meta descriptions
  • Which titles don't match what the page ranks for?
  • Find duplicate titles across our top pages

The playbook

Titles and descriptions are the only part of a page a searcher sees before clicking, and they are usually written before anyone knew what the page would rank for. Search Console tells you what it ranks for now. This playbook lines the two up.

Sequel supplies the query data. Reading the live titles uses your own browsing.

Steps

  1. Pull the top pages and their queries. google_search_console.query with dimensions: ["page"], 28 days ending 3 days ago, rowLimit: 200, then with dimensions: ["query", "page"], rowLimit: 5000. For each page keep its top five queries by impressions.

  2. Fetch each top page's head. Take the top 50 pages by impressions (state the number). Fetch each and extract the title, the meta description, the first H1, and og:title. Use sequel_workbench to loop if you can execute code.

  3. Run the checks per page.

    • Missing title or description.
    • Title or description duplicated across two or more pages (templates cause this).
    • Title over 60 characters or description over 155, which is roughly where Google truncates.
    • Title that starts with the brand name, pushing the topic out of view.
    • Title that contains none of the words from the page's top query.
    • Description that does not answer or mention the top query.
    • H1 that targets a different intent than the title.
  4. Prioritise by clicks at stake. Weight each finding by the page's impressions. Then compare the page's CTR to the site's median CTR at its rounded position (the method in ctr-underperformers); a page with a metadata finding and below-median CTR goes to the top.

  5. Report. A table sorted by impressions: page, top query, current title, current description, findings. Then rewrites for the top ten: a title under 60 characters that leads with the topic and includes the top query's words naturally, and a description under 155 that answers the query's intent. Show the current and proposed side by side.

Gotchas

  • Google rewrites titles it does not like, often when the title is stuffed, too long or duplicated. A clean, specific title is the best defence; do not respond to rewriting by stuffing harder.
  • Templates produce duplicates by design. A pattern like "Product | Brand" across a catalogue needs the template fixed, not each page.
  • Character counts are a proxy for pixel width. Wide letters truncate sooner. Treat 60 and 155 as guidance.
  • Titles rendered by JavaScript may not be in the fetched HTML. If the title element is empty in the source but present in the browser, say so; Google can render it, but it is slower and riskier.
  • Search Console lags 2 to 3 days. End the window 3 days back.

Install

Install Sequel skills into your agent

Pick your app and Sequel installs itself: a one-click link where the client supports it, that client’s own few steps where it doesn’t. The playbooks come with the server: your agent sees that this playbook exists and reads it when a question matches.

Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex, Grok, Muse, dots and any other MCP app

Already have an MCP client?

https://api.sequel.sh/mcp

Add it as a remote (streamable HTTP) server and sign in when prompted. Skills come with it; nothing else to install. Manual setup per client

Choose your app

  • Claude

    One click, opens in the app

  • Cursor

    One click, opens in the app

  • VS Code

    One click, opens in the app

  • ChatGPT

    Turn on developer mode, then add Sequel. About two minutes.

  • Claude Code

    Run one command, then sign in with /mcp.

  • Codex

    Run one command, then sign in.

  • Gemini CLI

    Run one command, then sign in with /mcp auth.

  • Grok

    Add Sequel as a connector and sign in.

  • Grok Bot

    Paste this to the bot. It registers Sequel and asks you to sign in.

  • Muse

    Muse writes its own connector. One message is the whole setup.

  • dots

    Add Sequel in ChatGPT; your dot picks it up with no extra step.

  • OpenCode

    Add Sequel as a remote server from the OpenCode CLI.

  • Other MCP app

    Any client that speaks remote MCP can connect with this URL.

More like this

Other SEO skills

Analyze high-ranking landing pages

See which pages perform best in organic search: the landing pages that earn the most clicks and impressions, the queries behind each one, and how they compare with competitor estimates from Ahrefs.

Audit internal links to important pages

Audit the site's own internal linking: crawl navigation and body links between the site's pages to find valuable pages with too few inbound internal links, orphan pages, and the handful of cross-links that would lift striking-distance rankings.

Audit or draft an llms.txt

Check whether the site has an llms.txt, whether it follows the spec and points at the pages that matter, and if it is missing draft one from the pages Search Console shows people actually find, so AI assistants get a curated map of the site instead of guessing.

Audit redirect chains and loops

Follow every redirect on the URLs Search Console still sends traffic to, on the sitemap, and on backlinked pages, to find chains, loops, redirects to the homepage, and temporary redirects that should be permanent, so link equity and crawl budget stop leaking.

Audit referring domain quality

Grade the domains linking to a site by authority, traffic and link count, spot concentration risk and link-farm patterns, and separate the referring domains that carry weight from the ones that are noise.

Backlink profile health check

See who links to the site and whether the backlink profile is healthy: referring domains, authority distribution, anchor text mix, dofollow share and concentration risk from Ahrefs, optionally compared against a competitor.

FAQ

Frequently asked questions

What is a metadata audit in SEO?
A review of title tags and meta descriptions across your top pages to identify duplicates, missing values, tags that are too long or too short, and titles that do not align with the queries the page actually ranks for. The goal is titles that match search intent and descriptions that earn clicks.
How long should a title tag be?
50 to 60 characters. Beyond 60, Google truncates it in the search result with an ellipsis, which usually breaks the meaning. Under 30 characters often means the title is too generic or not keyword-inclusive. The limit is pixel-based, not character-based, so short words can push the limit further.
Does Google always use my title tag?
No. Google rewrites titles it considers misleading, too keyword-stuffed, or a poor match for the query. If you see a different title in the search result than the one in your HTML, Google chose its own. The best way to keep your title is to write one that accurately matches the page content and query intent.
Should every page have a unique meta description?
Yes for your top pages. Google ignores duplicate descriptions and often rewrites them anyway, but a well-written description that includes the target query and a clear value proposition improves CTR. Focus effort on the pages that earn impressions.
Can an AI agent audit metadata across my top pages?
Yes. The agent fetches your top pages from Search Console, extracts titles and descriptions, checks lengths and duplicates, and compares titles against the queries each page ranks for. Sequel provides the Search Console connection and the metadata-audit playbook.

Put this playbook to work

Connect a source, ask the question, and the agent follows these steps. Free to start.