🧠 AI Learning Hub

Hub › Lessons › Content planning, lesson 6

Lesson 6 · AI for your content planningAbout 20 minutes

Check a planned title against what searchers want, before you write

You can write a good answer to a question and still choose a title that brings the wrong readers. People who type your title into Google may want something else: a how-to guide instead of an opinion, or a price list instead of advice. This lesson shows you how to check, in about 20 minutes, before you write. You look at the real results yourself, write one line about each, and use a prompt to compare them with what your post will cover. It does not predict rankings or traffic. Nobody can promise those.

What you will be able to do: say whether a planned title is a Match, Partly or Different from what searchers want, based on results you looked at yourself, and pick a clearer title that only promises what your post covers. You also get the searchers' questions your post does not answer, so you can decide whether to add them.

Step 1: Write down the title and the searches (3 minutes)

Step 2: Look at the real results and take notes (10 minutes)

Google says that to return relevant results it first works out "the intent behind your query". You are doing the same thing by hand.

Step 3: The check prompt

Fill in each line, add one line per result under the notes, then paste it into your AI tool. The AI only sees your notes, so the check is as good as they are.

Prompt: search intent check
Help me check whether a title I plan to write matches what people searching for it want. Use only my notes below.

My planned title:
What my post will cover (2 or 3 lines):
The searches I tried:
My notes on the search results (one line per result: type of page, who wrote it, its main answer or angle):
-
"People also ask" or related questions I saw:
-

Return these parts:
1. What searchers seem to want: 1 to 3 points. After each point, give the numbers of the result notes that support it.
2. Verdict: Match, Partly or Different, judged on the question the results answer, not on their answer.
   - Match: more than half of the results answer the same question my post answers.
   - Partly: some results answer my question, but half or fewer.
   - Different: no more than one result answers my question.
   Give one sentence explaining the verdict with result numbers. Then one sentence on how my answer compares with the answers in the results. A different answer is fine; just say so.
3. Title options: up to 3 titles for the post I described. Each must be something my post will actually cover. After each, say in a few words which searcher need it fits.
4. Questions my post does not answer: questions from my notes that searchers ask and my post does not cover. I will decide whether to add them.
5. Not checked: one line on what this check cannot tell me.

Rules:
- Use only my notes. Do not add results, websites, facts or numbers that are not in my notes.
- Do not predict rankings, traffic, clicks, search volume or how hard it is to rank.
- Do not suggest a title that promises something my post will not cover.
- If I gave notes on fewer than 5 results, say that the notes are too few to judge and stop after part 1.

Step 4: Decide what to do (5 minutes)

Worked example

We checked two planned titles for the same made-up web designer from lesson 5. The business and its posts are illustrative. The search results are real: we searched google.com.sg in English on 29 October 2026 and wrote one line per result, in our own words. Results change over time and by location, so yours will differ.

Input: notes for "Should your menu page show prices?"

Sample input (real results, our notes)
My planned title: Should your menu page show prices?
What my post will cover (2 or 3 lines): For small cafes and home food businesses in Singapore that have, or are planning, a website menu page. My answer: yes, show prices if you can, because most people check the price online instead of calling. Price changes are included with my basic site, so changing prices is not a reason to hide them. Offer: tell me what you sell and I will tell you how I would lay out the page.
The searches I tried: should i put prices on my cafe website menu (google.com.sg in English, 29 Oct 2026)
My notes on the search results (one line per result: type of page, who wrote it, its main answer or angle):
1. Reddit small business discussion started by someone who builds restaurant websites: show prices or say "contact for a quote"? Top answer: the writer says they leave any website that does not list prices.
2. Guide by a menu design company about how to set cafe menu prices (Google showed "Missing: website").
3. Quora question: why do some restaurants show menus without prices on their website? Top answer: some very high-end restaurants do this on purpose.
4. Guide by a digital menu company: cafe menu pricing, menu engineering and pricing psychology.
5. Article by a web designer: what every cafe website needs. Answer: yes, show prices; also mentions adding menu items and prices to a Google Business Profile.
6. Facebook food group discussion: why don't restaurants list prices on their websites? Top answer: no prices makes them assume it is expensive.
7. Blog by an online ordering company: how to set menu prices using food cost.
8. Blog by a restaurant booking software company: pricing psychology for menus.
9. Guide by a food business site: how to price your restaurant menu, with food cost percentages.
"People also ask" or related questions I saw:
- What is the ideal pricing strategy for a cafe?
- What is a reasonable price to charge for a website?
- How do I price my menu?
- How many items should be on a cafe menu?

Output (as returned)

Shown word for word from our test with Claude; only the formatting was converted for this page.

1. What searchers seem to want

2. Verdict: Partly

Only 1, 3, 5 and 6 deal with whether to show prices on a website, which is 4 of 9. Results 2, 4, 7, 8 and 9 answer how to set prices, which is a different question. Even if you count only 1 and 5 as the same question, the verdict stays Partly.

Your answer (yes, show prices) agrees with 1 and 5, and 6 backs it by saying missing prices make people assume it is expensive. Result 3 is the only one that gives a reason to hide prices, and it applies to very high-end places.

3. Title options

  1. Should a cafe website menu show prices? Yes, and here's why. It fits searchers who want a direct yes/no (1, 5).
  2. Should your menu page show prices? A guide for small cafes and home food businesses in Singapore. It fits owners who want an answer for their size of business.
  3. Worried about changing prices? Why that's no reason to hide them on your menu page. It fits owners who hesitate over keeping prices up to date.

4. Questions your post does not answer

5. Not checked

This check uses one search (google.com.sg, English, 29 Oct 2026) and your one-line notes on 9 results. It can't tell you what the pages actually say beyond your notes, or what other wordings of the question would show.

What we checked

What we would do with this: the post answers "should prices be shown", but more than half of these results are about "how to set prices". Title option 1 or 3 makes the question clearer. "How do I price my menu?" is a different post, and the web designer should only write it if they can answer it from real experience.

The other title we checked

For "Do I need a website if I already have Instagram?" (search: "do i need a website if i have instagram", same day), all nine results we noted answered that question, and both test runs gave Match. Almost every result was written by a web design or website company, and most said yes, you need a website. The planned post says Instagram may be enough until customers keep asking the same questions. That different answer is fine; both outputs suggested a title that shows it, such as "Instagram or a website for your home bakery or cafe: when DM orders are enough".

What we changed after testing

The prompt above is the third version. We ran each version twice on both titles:

Watch out for

Next step

How we checked this lesson