Best practices for writing content for SEO and marketing

What this guide gives you

Actionable steps to plan, draft, optimize and verify content so it answers real user intent, performs well on modern search features (including AI Overviews), and is robust for mobile-first indexing.

Plan: audiences, intent and research

Start with clarity about who you're writing for and why they will choose your content. Map a primary user intent (informational, transactional, navigational, or investigational) and design the content to satisfy that intent before you worry about keywords.

Research checklist:

• Define the target audience and the exact question they need answered.
• Collect real user queries and phrases tied to intent, then group them by topic rather than chasing single keywords.
• Audit competing pages: note what they cover, what they miss, and where you can add unique value or updated examples.
• Decide the content format and depth based on user intent: quick answer, how‑to, long-form guide, checklist, comparison, or landing page.

Write: structure, clarity and persuasion

Draft with a clear structure: a concise lead that answers the user's question, scannable headings, and a logical progression. Use short paragraphs, descriptive H2/H3 headings and bullet lists where helpful.

Headlines and subheads: write them for humans first. Use headings to reflect the content beneath them and include primary topic signals naturally rather than stuffing keywords.

Make facts verifiable: when you state a claim, link to the source, include a date for time-sensitive statements, and keep a short bibliography for research-heavy pieces.

Internal and external links: link to relevant pages on your site to help users explore related topics and to clarify your content hierarchy. For external links, use standard HTML. Examples:

A standard link without a rel attribute: example. For paid placements use: example. For user-generated links use: example. To mark a non-editorial hint use: example.

Note: there is no rel="dofollow" attribute. rel="nofollow" is treated by Google as a hint; rel="sponsored" should be used for paid or compensated links.

Optimize: on-page signals and structured data

On-page optimization should be about helping users and machines interpret your content. Meta title and description should summarize the page’s value for the chosen query; keep them accurate and avoid clickbait.

Structured data: use Schema.org where it adds clarity (article, FAQ, product, how-to). Validate with the Rich Results Test and the Schema Markup Validator before publishing.

Mobile-first indexing and performance: Google uses the mobile version as its primary basis for crawling and indexing; since July 2024 Google crawls sites for Search with Googlebot Smartphone by default. Prioritise responsive layout, readable font sizes, and fast load times.

Core Web Vitals and interaction metrics matter for user experience. Measure LCP, INP and CLS with Lighthouse or Chrome DevTools, and fix high-impact issues before large-scale publication.

Publish and verify: checks before and after launch

Pre-publish checklist:

• Confirm the URL returns a 200 status and the expected canonical tag.
• Run the Rich Results Test and fix structured-data errors.
• Measure Core Web Vitals in Lighthouse and address the largest regressions.
• Check mobile rendering in Chrome DevTools and confirm content is accessible without requiring extra interactions.

Verification commands and tools (examples you can run): use curl -I https://example.com/page to inspect response headers only. To fetch the HTML a specific user-agent receives, use curl -A "Googlebot Smartphone" https://example.com/page. Use Chrome DevTools Elements to review the rendered DOM and ensure content isn’t hidden behind client-side interactions.

Indexing checks: if you own the property, use the URL Inspection tool in Google Search Console for an authoritative view of how Google last saw the URL. For third‑party pages you do not control, the site: operator can provide a public indication that Google knows about the page, but it is not definitive.

AI-assisted writing: workflow and guardrails

AI can accelerate drafting and ideation, but human oversight is essential. Use AI to produce outlines, variants of headlines, or to summarise research; always fact-check, verify citations, and edit for voice, accuracy and completeness.

Editorial guardrails sample:

• Require source links and date stamps for any factual claims produced by AI.
• Ensure an editor verifies the article answers the target intent and that examples are current.
• Maintain an issue log for corrections so updates are traceable.

Common mistakes and how to avoid them

• Writing for a keyword instead of an intent: focus on the user question and map supporting headings to sub-questions.
• Publishing without checking mobile rendering: test in Chrome DevTools and on real devices.
• Using AI output verbatim: always fact-check, add first-hand expertise, and edit for clarity.
• Relying solely on third‑party authority metrics: treat DA/DR as industry metrics, not Google signals.

Publishing checklist (quick)

• Lead answers the primary user question immediately.
• H2/H3 hierarchy maps to subtopics; each section has at least one clear takeaway.
• Meta title and description are accurate and not misleading.
• Structured data validated; performance checks green or prioritized for fixes.

Measuring success and iterating

Set measurement goals tied to intent: search impressions and clicks for discovery, engagement metrics and conversions for transactional pages, time on page for deep informational content. Use the Performance report in Google Search Console for query and page-level trends where you own the property.

Use A/B testing for major changes to page templates or CTAs. Iterate based on user behaviour and search performance, not on vanity metrics alone.

Further reading and tools

Use these tools in your workflow: Chrome DevTools and Lighthouse for rendering and performance checks, Rich Results Test and Schema Markup Validator for structured data, and curl for quick header and HTML inspections. For owned properties, use Google Search Console URL Inspection and the Performance report.

FAQ

How long should a piece of content be for SEO?

There is no single ideal length. Choose depth that satisfies the user intent: quick answers can be short, while decision-making or research pieces require more breadth and evidence. Prioritise completeness, clarity and unique value over arbitrary word counts.

Do I need structured data on every article?

Use structured data when it accurately describes the content (article, FAQ, how-to, product). Structured data can make your content eligible for rich displays, but incorrect or irrelevant markup can cause issues. Validate with the Rich Results Test before publishing.

How should I use AI when writing?

Use AI for ideation, outlines and draft variants, then apply human review for accuracy, sourcing and voice. Keep an editorial process that enforces fact-checking and attribution for any factual claims AI produces.

How can I tell if Google has indexed my page?

If you own the site, use the URL Inspection tool in Google Search Console for an authoritative view. For pages you don't control, the site: operator may indicate public index signals but is not definitive; use it only as a quick public check.