Writing a page for a keyword without looking at what ranks is guessing. Writing one by copying the top result gives you a worse version of something that already exists. The useful middle is to read the first few results, work out what searchers seem to want and find what none of them answer.
That reading takes an hour. An assistant can do the sorting from the headings and features you paste in. It cannot see live search results, volumes or difficulty, and the prompt is written so it never makes those up.
What you need
- Your target keyword or question.
- A line on the business and the audience the page is for.
- The top three to five results. Search the keyword in your browser, open each page and paste its title, its H1 and H2 headings, and any lists, tables or FAQs. If your chatbot can browse, you can give it the URLs, but check what it says it read.
The prompt
Paste this into a new chat, then fill in the fields and paste the pages.
You write an SEO content brief from the pages that currently rank. You cannot see live search results, volumes or difficulty, so never state them or invent what ranks.
Target keyword or question: [ ]
The page is for: [business and audience, and page type if known]
Top results (title, headings, notable features, one block per page):
[paste]
Do this:
1. For each result: title, H1 and H2 in order, rough word count if you can tell, format, and anything distinctive (calculator, table, data, video, definition up top).
2. Classify the intent (informational, commercial investigation, transactional, local) and give the evidence. If intents are mixed, say which to serve.
3. Coverage table: topics across the results with a count of pages covering each. Mark table stakes (3 or more), common (2) or rare (1).
4. Gaps: what a reader would likely want that few or none give. Tie each to what you saw missing and label it your judgement, not data.
5. Outline: 3 title options under 60 characters, an H1, H2s with one line each on what the section must answer, and where a table, example or checklist helps. No padding.
6. Questions to answer: those in the pages' own headings or FAQs, and any you add (label yours).
7. Terms and entities that recur across the results. Only those you saw.
8. A meta description under 155 characters and 3 internal-link slots described by topic.
End with "Not known": volume, difficulty, freshness, backlinks, anything missing from what I pasted.
Do not copy sentences from the pages. No invented statistics, tools or traffic claims. Do not promise rankings. No em dashes.
How to check the result
Look at the intent first. The prompt asks for evidence. If it says the intent is informational, it should point to what the pages are: guides, definitions, how-tos. If the results are mixed, decide which intent you are serving and stick to it.
Then read the coverage table. Topics covered by three or more pages are table stakes: leave them out and your page looks thin. Topics covered by one page are chances to stand out.
The gaps section is labelled as the assistant's judgement, not data, and that is correct. Treat each gap as a question to answer, and check that real readers would want it. A gap exists for a reason sometimes: nobody wants it.
Use the outline as a skeleton and write the page yourself, with your own examples and facts. The prompt is told not to copy sentences from the pages, and you should not either.
Finish with the "Not known" list. Volume, difficulty, freshness and backlinks are all outside what you pasted. If they matter to the decision, use a search tool that shows them.
Limits
- It cannot see live search results, so everything depends on the pages you paste.
- It does not promise rankings, and no brief can.
- The meta description it writes is a draft. Count the characters and read it as a searcher would.
- It does not write the page.
Browse all skills in the catalog
Want this as a ready-made skill? Search Intent Page Brief (Free) does it in your own assistant.
Follow for new free skills
New free skills and guides appear in all of these as we publish them. Pick whichever you already use.
- RSS feed for any feed reader
- Watch the free skills repo on GitHub
- Follow on Gumroad