Everything you control on a page to clarify meaning and improve eligibility. Think titles, meta, headings, links, media, structured data, and performance. See Google’s Search Essentials.

How the page reads and behaves for humans. Structure, scannability, contrast, accessible components, and clear next steps. NN/g explains scanning in the F-pattern study.

A short definition or step list near the top that a busy person can use without scrolling. Useful for readers and for synthesized answers.

Write titles that match the page

• Front-load the main term and keep the promise of your H1.
• Avoid boilerplate that hides meaning. Google explains how titles may be shown in title links.
• Prefer human clarity over keyword stuffing. Keep it natural.

Meta descriptions that earn clicks

• Summarize the outcome in one or two sentences.
• Use verbs and mention the audience or role where relevant.
• Google may rewrite snippets, yet good meta text still helps. See snippet guidance.

Structure for scanning

• Use one H1 per page, then H2 sections with short labels.
• Put a one sentence answer or a 3 step list near the top.
• Mirror People Also Ask phrasing in a compact FAQ later.

Pattern

<h1>What is product onboarding</h1>
<p><strong>Short answer:</strong> Onboarding helps users reach first value by...</p>
<ol><li>Define first value</li><li>Guide setup</li><li>Measure activation</li></ol>

Make links crawlable and descriptive

• Use real anchors with href attributes. Avoid click handlers without URLs.
• Put the important words in the anchor. Google’s note on crawlable links explains why.
• Link hubs to spokes and spokes to siblings to build context.

Anchor text examples

• Good: compare analytics tools instead of click here.
• Good: onboarding checklist instead of this post.

Images

• Use descriptive alt text that states the insight, not just the object.
• Compress and serve modern formats. Faster media helps Core Web Vitals.

Tables

Tables are perfect for comparisons and steps. Add headers, captions, and scope attributes for accessibility. See the W3C’s tables tutorial.

Captions

Write the takeaway under charts and screenshots. People read captions even when they skip paragraphs.

Compact FAQ

• Use questions that mirror how buyers ask.
• Keep answers under 80 words where possible.
• Place FAQ near the end so it does not interrupt the flow.

Schema choices

• Article for guides and posts.
• FAQPage for clear Q and A blocks.
• BreadcrumbList for hubs and spokes.

WCAG basics

Follow the Web Content Accessibility Guidelines for contrast, keyboard access, focus order, and semantics. See the W3C overview of WCAG.

Core Web Vitals

• LCP target 2.5s or faster
• INP target 200ms or faster
• CLS target 0.1 or lower

Learn more at web.dev.

Reader-first patterns

• Short paragraphs and meaningful subheads.
• Tables for comparisons and steps.
• Clear CTAs that match intent.

Search Console

• Track queries per page in the Performance report.
• Check Page indexing and enhancement eligibility.
• Use URL Inspection to see rendered HTML.

Analytics

• Clicks from content pages to pricing and demos.
• Time on page and scroll depth to the answer block.
• Assisted conversions using GA4 attribution models.

Quality checks

• Title and meta duplication rate.
• Broken links and redirect chains.
• Alt text coverage and table header usage.

Days 1 to 30

• Audit titles and meta for top 50 pages and fix duplication.
• Add answer blocks and compact FAQs to 10 key pages.
• Validate schema on those pages and submit for indexing.

Days 31 to 60

• Standardize internal link anchors across one cluster.
• Refactor tables with headers, captions, and scope.
• Improve LCP and INP by compressing media and trimming scripts.

Days 61 to 90

• Extend the checklist sitewide and monitor Search Console deltas.
• Publish a style guide for headings, anchors, alt text, and schema.
• Review pipeline assists from improved pages with sales.

Will Google always use my title and meta

Not always. Titles and snippets may be adjusted based on the query and the page. Write accurate text anyway so the system has the right signals. See title links and snippets.

Do tables and FAQs help with visibility

They improve clarity and can support eligibility when paired with valid structured data. Markup must match what users see and follow Google’s policies.