How to Audit Title Tags and H1s Using Google Search Console Data

Use Search Console queries, CTR and page performance to prioritize title tag and H1 audits without blindly rewriting metadata.

TL;DR

Use Google Search Console to identify pages worth reviewing, not to automatically rewrite every title or H1. Start with important query-and-page pairs, compare complete time windows and positions, then inspect the live title, main heading and content. Improve clarity and search-intent fit only where evidence supports a change. Search Console does not directly tell you that a particular title tag caused a low CTR.

Why a title audit should start with search data

A website audit tool can list every title tag longer than an arbitrary character count. That is sometimes helpful for finding obvious mistakes. But a page with a short title may perform well, while a technically perfect title may describe the wrong thing.

Google Search Console adds context. It shows which pages receive impressions, which queries are associated with them and how frequently searchers click.

That lets you prioritize pages with meaningful visibility and business value. Rather than rewriting a hundred titles because a crawler flagged their length, you can investigate the ten pages where better clarity could matter.

The goal is to make each result and page understandable to real people, not to manipulate one SEO score.

Know the roles of the title tag and H1

The HTML <title> element commonly supplies a candidate title link in Google Search. Google can generate title links from other page information, including visible headings and other signals. The title you write is not a guarantee of exactly what every user will see.

The <h1> is usually the page’s main visible heading. It tells visitors what the content is about. A clear H1 helps the reader quickly confirm that they reached the right page.

They can be similar without being identical. A product feature page might use a concise heading and a more descriptive title that includes the product name.

Google’s title-link documentation explains that title generation uses multiple sources and recommends descriptive, concise text rather than boilerplate or keyword repetition.

Step 1: select pages that matter

Open Search Console’s Performance report and choose a complete 28- or 90-day period. Start with pages that have meaningful impressions and contribute to your business goal.

For a SaaS website, consider product features, comparisons, integrations, pricing and important tutorials. For an online store, categories and major product pages may be more relevant.

Do not focus only on the highest-impression pages. A niche integration guide with moderate search volume can attract better-qualified visitors than a broad informational article.

Create a shortlist of ten URLs with the following columns: page, clicks, impressions, CTR, average position and primary search intent.

Step 2: examine query-and-page pairs

For each candidate, open the Queries tab or request Search Analytics grouped by page and query through the API.

Look at the terms that actually produce impressions. They may reveal a different audience than you expected.

For example, a page titled “Marketing Automation” could be receiving visibility mainly for “schedule LinkedIn posts automatically.” If the content is specifically about scheduling, the title might be too vague.

But do not automatically insert the entire query into every title or heading. The goal is to represent the actual page clearly, not to repeat exact phrases regardless of context.

If the page ranks for multiple legitimate intents, decide which one it is supposed to serve before editing.

Step 3: interpret CTR in context

CTR is clicks divided by impressions. It depends on many things: ranking position, brand familiarity, query intent, result features and the searcher’s device.

A page with a 1% CTR at average position 17 may be ordinary. A page with 1% CTR at a strong average position for a highly relevant commercial query may deserve a closer look.

Also compare periods. If impressions stayed relatively stable and CTR declined, a title-link or result-presentation review can be reasonable. If average position fell sharply, the issue may be broader than metadata.

Do not compare unrelated queries as if they had one universal CTR benchmark. Branded navigational searches and broad informational questions behave differently.

See our low-CTR workflow for a more careful method.

Step 4: inspect what Google actually displays

Search the relevant query and look at the result when you can reproduce it. Google may show a title link different from your HTML title.

Check whether the snippet accurately describes the page, whether the displayed title is truncated and whether competing results use clearer language. Remember that results can vary by location and device.

Avoid claiming a screenshot represents every user’s result. Your aim is to identify obvious mismatches or ambiguous wording, not reconstruct an exact universal SERP.

If Google is rewriting your title, review its guidance. The problem may be a repetitive template, missing specificity or disagreement between the title and visible heading.

Step 5: review the rendered HTML

Inspect the current title tag and visible H1 on the live page, not only in the source repository. Templates sometimes override metadata or render a different value in production.

Check for duplicate titles across genuinely different pages, generic headings such as “Welcome,” and page titles that promise something the content does not provide.

Also look for unintended noindex or canonical issues if the page’s visibility changed materially. A title rewrite cannot fix a page whose canonical unexpectedly points somewhere else.

An SEO audit should distinguish an HTML issue from a content issue. A title can be technically correct but fail to explain what readers gain.

A worked example from a product website

Suppose an integration guide receives 1,800 impressions for setup-related queries, with a CTR below comparable results. Its title reads “Integration | Product Name,” while the H1 says “Get Started.”

A clearer pair could be:

Title: “Connect Google Search Console to Claude Code | Product Name”

H1: “How to connect Google Search Console to Claude Code”

These examples are only appropriate if the article actually explains that setup process. The title should not advertise Claude Code if the page covers only ordinary Claude chat.

The improvement is clarity and alignment. It is not a claim that changing a tag will automatically increase ranking or clicks.

How to handle page templates and duplicate titles

A site with thousands of pages may generate titles through a shared template. A bug can cause dozens of product pages to use identical text, making results less distinguishable.

Investigate whether the duplicates are genuine duplicates or different pages that deserve unique descriptions. If the latter, fix the title generation at template level rather than editing every page manually.

For category pages, combine the meaningful category name with the site’s brand when appropriate. Avoid stuffing the same generic sales phrase into every title.

Also make sure the H1 remains understandable when the template is used on mobile. A short, readable heading is often more helpful than one designed purely for a crawler.

Use AI to prepare suggestions, not unreviewed edits

With Search Console data and access to your page content, an AI assistant can assemble a useful shortlist and draft alternatives.

Use a prompt like this:

For my selected Search Console property, find commercially relevant pages with substantial impressions and potential CTR issues across the last 28 complete days. Return URLs, leading queries, clicks, impressions, CTR and position. After examining the actual page content and existing metadata, suggest at most five title and H1 improvements. Explain the search intent and do not promise a specific CTR gain. Do not modify files without review.

If the agent cannot inspect page content, it should not invent an existing H1. Give it the HTML or let a properly authorized coding tool inspect the file.

GSC Magic’s tools documentation includes CTR-outlier and performance reporting. These can surface candidates, but they do not replace reading the page.

Test and measure changes properly

Record the old title, new title, reason and implementation date. After deployment, confirm that the rendered HTML contains the intended values.

Allow time for Google to process the page. Then compare relevant query-and-page performance over complete periods, controlling as far as practical for ranking and search demand changes.

If CTR improved but impressions and query mix also changed, do not attribute the whole movement confidently to one title edit. SEO testing in uncontrolled search results is noisy.

The outcome may be clearer messaging even if the short-term traffic change is small. That is still useful when the page helps prospective customers.

FAQ

Does every page need exactly one H1?

A clear main heading is good for usability and structure. Google’s ranking systems do not require a mystical one-H1 formula to understand a page.

Should the title and H1 be identical?

Not necessarily. They should accurately represent the same page and audience; each can serve a slightly different presentation need.

Does Search Console show my HTML title?

No. It reports search performance. You must inspect the page or use an appropriate crawler or source-code tool to retrieve metadata.

Is low CTR proof that the title is bad?

No. Position, intent, query mix and result features influence CTR. Treat it as a signal for investigation.

Should I add the current year to every title?

Only when recency genuinely matters and the content is current. Changing the year without updating the information is not helpful.

Fix clarity, not a numeric SEO score

Start with pages that matter commercially and have enough search data to support a useful review. Align their titles and headings with what readers actually need, then measure changes carefully.

For more ideas, continue with striking-distance keyword research or the GSC quick-wins checklist.

Join the waitlist

Coming soon. Get 30% off Pro for 6 months when you join.

Join the waitlist