Skip to content
Chalk Labs / AI SEO
How-to guide

How to Write How-To Pages That Get Cited

By Rahil Jain, founder of Chalk LabsUpdated How we research

The short answer

A how-to page gets cited when its title matches the task, its first lines give the outcome and time needed, and each step is a single action that names the exact tool, setting or number. Add a way to check the result, show that you did the task yourself, and keep the page current. Schema is optional.

  • Match the title to the task as people phrase it, and put the result and time needed in the first lines.
  • Write one action per step, with the exact tool, menu path or value, and a check that it worked.
  • Show first-hand experience: what you did, when, and what went wrong.
  • HowTo schema no longer earns a Google rich result, so treat it as optional.

What makes a how-to page citable?

Two things: it matches the task, and it is easy to lift in pieces. An Ahrefs study of 1.4 million ChatGPT prompts found cited URLs had higher title similarity to the prompt than non-cited ones, 0.602 against 0.484 1. Titles scored highest, at 0.656, against the sub-searches ChatGPT ran itself 1.

Ahrefs used open-source embeddings to approximate how ChatGPT judges relevance, on prompts from February 2025, and compared cited with non-cited pages across all source types. That is a rough proxy, so treat the numbers as direction 1. Search results with natural-language URL slugs were cited 89.78% of the time, against 81.11% for those without 1. Name the task in plain words in the title, the heading and the URL.

Do it step by step

0 of 8 done0%

  1. Write the title as 'How to [do X] in [tool or context]'. Check it against real phrasing in search suggestions and customer emails.

    Tip: Use the same words in the title, first heading and URL slug.

  2. Write one sentence on what the reader will have at the end, one on how long it takes, and one list of what they need.

  3. Complete every step on a clean setup. Note exact labels, values, times, and anything that failed. Take screenshots.

  4. Start each step with a verb. Name the tool, menu path and value. Add a tip only when it prevents a real error.

  5. Say what the reader should see if the step worked. Add what to do if they do not see it.

  6. Give the date, tool version and one thing that went wrong. Link to the vendor's documentation for anything you did not test.

  7. If your system makes it easy, add JSON-LD that mirrors the visible steps exactly. Validate it, then forget about it.

  8. Put a visible updated date on the page and a reminder in your calendar to retest the steps in six months.

Your ticks are saved in this browser only.

Copy-ready templates

How-to page outline

markdown
# How to [do X] in [tool]

**Result:** [what you will have at the end]
**Time:** [about N minutes]
**You need:** [tool, access, file]

## Steps
1. [Verb + exact action + exact value]. Check: [what you should see].
2. ...

## How to check it worked
[One observable test]

## If it did not work
[Top 2 causes and fixes]

## How we tested this
[Date, version, what went wrong once]

Last updated: [date]. Change: [one line].

Fill every bracket. If you cannot fill 'Check', the step is not ready.

Minimal HowTo JSON-LD (optional)

json
{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to check robots.txt for AI crawler rules",
  "totalTime": "PT10M",
  "step": [
    {
      "@type": "HowToStep",
      "name": "Open the file",
      "text": "Go to yoursite.com/robots.txt in a browser."
    },
    {
      "@type": "HowToStep",
      "name": "Look for blocks",
      "text": "Search for GPTBot and OAI-SearchBot and remove any Disallow: / line under them."
    }
  ]
}

Wrap in a script tag with type application/ld+json. The steps must match the visible page. Google no longer shows a rich result for HowTo.

Step-quality checklist

markdown
- [ ] Starts with a verb
- [ ] One action only
- [ ] Names the tool, menu or value
- [ ] Has a visible check
- [ ] Warning comes before the risky action
- [ ] Tested by a person, with date

Run each step through this before publishing.

How should you structure the page for AI tools?

Break it into self-contained pieces with clear headings. Microsoft's Bing team says AI assistants do not read a page top to bottom like a person, and that selection happens at the level of passages 2. It recommends specific headings over vague ones like 'Learn More' 2.

Open with the outcome, the time needed and the tools. Then give numbered steps. Finish with how to check the result and what to do if it fails. That order matches how people ask: what will I get, what do I need, how do I do it, how do I know it worked.

How specific should each step be?

Specific enough that a stranger can do it without guessing. Name the button, the menu path, the setting and the expected value. 'Optimise your robots file' fails; 'open yoursite.com/robots.txt and check that no line says Disallow: /' passes.

Give each step one action and one observable result. Put warnings before the step they affect, not after. Include the typical time per step if you know it, and say plainly when you do not.

Vague step versus specific step
  • Vague: Make sure AI bots can access your site.
  • Specific: Open yoursite.com/robots.txt. Search for 'GPTBot' and 'OAI-SearchBot'. If either has 'Disallow: /' under it, remove that line, save, and reload the file to confirm.
  • Check: The file no longer shows Disallow: / under those agents. Only do this if you want those bots to crawl. Many sites block GPTBot on purpose and allow OAI-SearchBot; see [block AI training but allow AI search](/ai-seo/how-to/block-ai-training-but-allow-ai-search).

How do you prove you did the task yourself?

Say what you did and show the evidence. Google's content guidance asks whether content shows expertise from direct experience, whether authorship is clear, and how it was created, including how many products were tested and how 3. It also asks for background on how automation or AI was used 3.

Add a short 'how we tested this' note: the date, the version of the tool, and one thing that went wrong. Screenshots, error messages and before-and-after values are worth more than general advice. If you have not done the task, say that your steps come from the vendor's documentation and link to it.

Do you still need HowTo schema?

No. Google's changelog records that it removed its How-to structured data documentation on September 14, 2023, because the feature is no longer shown in search results 4. Its AI features guide says no special schema.org markup is needed for AI Overviews or AI Mode 5.

Schema.org still defines HowTo as instructions that explain how to achieve a result by performing a sequence of steps 6. If you add it, keep the markup matching the visible text, which Google lists as a best practice 5. Use it as tidy labelling, not as a ranking tactic. The template below shows a minimal version, and how to add HowTo schema goes deeper.

How often should you update a how-to page?

Whenever the tool, screen or rule changes, and at least twice a year. Profound found explainers, how-tos and documentation had a median citation half-life of 28 days among sustained pages, close to other page types 7. These are vendor figures and the gaps are small 7.

Put a visible date and a one-line change note on the page. Fix broken steps first, because a step that no longer works is the fastest way to lose a reader and a citation. See how to refresh old content for AI.

What are the most common mistakes?

The most common is a story before the steps. Readers and AI tools both want the answer first, so move the narrative below the steps. The second is merging several tasks into one page; one page should answer one task.

The third is steps with no check. If a reader cannot tell whether a step worked, the page cannot be trusted. The fourth is copying another page's steps without testing them. For the opening lines, use answer-first introductions.

When is a how-to page the wrong format?

Use another format when the buyer is choosing, not doing. A choice needs a comparison page. A rule or definition needs a short explainer. Also skip the page if you cannot name a single observable result, because then the steps are really opinions.

Frequently asked questions

How long should a how-to page be?

As long as the task needs, no longer. Google asks whether readers leave feeling they learned enough to reach their goal 3. A clear result, as many tested steps as the task needs (most of ours run to eight) and a check usually serve readers better than a long essay.

Should I use numbered steps or paragraphs?

Use numbered steps for the actions and short paragraphs for the reasons. Numbered steps make each action easy to quote and follow, and a paragraph can explain why a step matters.

Do videos help how-to pages get cited?

They can, but we hold no verified figures for how-to videos in this guide. Add a text version of the steps so a reader, or an AI tool, can use the page without playing the video.

Is HowTo schema worth adding?

It is optional. Google stopped showing the HowTo rich result 4, and its AI features need no special markup 5. Add it only if it costs little and mirrors the visible steps.

Can I use AI to draft how-to steps?

You can draft with it, but test every step yourself. Google says generative models predict likely words and do not retrieve facts, and advises manual fact-checking of AI content 8.

About the author

Rahil Jain

Rahil Jain is an AI SEO (answer engine and generative engine optimisation) consultant and co-founder of Chalk Labs.

LinkedIn · Method and credentials

Sources

  1. Why ChatGPT Cites One Page Over Another (Study of 1.4M Prompts) · AhrefsOpened October 20, 2026. Supports: Published 15 April 2026: title similarity to the prompt 0.602 for cited vs 0.484 for non-cited URLs; 0.656 against fan-out queries; natural-language slugs had an 89.78% citation rate vs 81.11% without; relevance approximated with open-source embeddings.
  2. Optimizing Your Content for Inclusion in AI Search Answers · Microsoft Advertising (Bing)Opened October 20, 2026. Supports: Published 8 October 2025 by Krishna Madhavan: AI assistants do not read top to bottom; passage-level selection; specific headings over vague ones.
  3. Creating helpful, reliable, people-first content · Google Search CentralOpened October 20, 2026. Supports: First-hand expertise, clear authorship, disclosing how content was created including tests and AI use; last updated 2026-10-05.
  4. Search Central documentation updates · Google Search CentralOpened October 20, 2026. Supports: On 14 September 2023 the How-to structured data documentation was removed because the feature is no longer shown in search results.
  5. AI features and your website · Google Search CentralOpened October 20, 2026. Supports: No additional requirements or special optimisations for AI Overviews and AI Mode, no special schema.org markup needed; structured data should match visible text. Last updated 2025-12-10.
  6. HowTo · Schema.orgOpened October 20, 2026. Supports: HowTo defined as instructions that explain how to achieve a result by performing a sequence of steps; properties step, tool, supply, totalTime.
  7. The half-life of an AI citation is 11 days · ProfoundOpened October 20, 2026. Supports: Explain pages (explainers, how-tos, documentation) had a 28-day median half-life among sustained pages; vendor study.
  8. Google Search's guidance on using generative AI content on your website · Google Search CentralOpened October 20, 2026. Supports: Generative models predict likely word sequences and do not retrieve facts; critical to manually fact-check AI content. Last updated 2026-10-01.
How this page was made. Built on Rahil Jain's AI SEO method and drafted with AI research assistance. Every statistic links to the page we read it on (opened October 20, 2026 or nearby). Published October 20, 2026; last updated October 20, 2026. Chalk Labs sells AI SEO services, so we have a commercial interest in this topic. Spotted an error? Tell us and we will fix it.