The Blog Post Trap: Why AI Search Ignores Long Guides From Accountants and Solicitors
Accountants and solicitors keep publishing long guides hoping AI search will notice. ChatGPT and Google's AI Overview keep citing a different page format entirely, one that costs a fraction of the effort.
A regular question at accountancy and law firms with a marketing budget is why the blog is not paying off. Partners are told a guide builds authority, so someone on the team writes fifteen hundred words on inheritance tax planning or a change in employment law twice a month. Then a client asks ChatGPT which local accountant handles inheritance tax and the firm never comes up, despite that guide sitting right there on the site.
The Content Effort Is Going to the Wrong Format
AI answer engines are not reading your blog the way a prospective client would. They pull short, self contained answers out of your pages and match them to a question. A fifteen hundred word guide written as one flowing narrative rarely produces a clean answer a model can lift. A short, direct question paired with a direct answer does that job far more reliably.
1. What ChatGPT Actually Extracts From a Page
A large language model answering a search style question does not summarise your entire article. It pulls the smallest chunk of text that answers the question cleanly, a sentence or two with a clear claim and no throat clearing first. A page written as continuous prose forces the model to guess where the answer starts and ends. A page written as question, then plain answer, removes the guesswork entirely.
2. The Format That Gets Lifted Into an Answer
Firms that show up in AI answers write pages built around the exact questions clients ask, not around a topic. That means:
- State the question the way a client would actually type or ask it
- Answer it in the first sentence, plainly, before explaining further
- Keep each answer under one hundred words before adding detail
- Name the firm and its location inside the answer itself, not just the page title
- Mark the page up with FAQPage schema so the structure is explicit, not implied by formatting
3. Where This Beats the Long Guide
Put the two formats side by side and the gap is not subtle.
| Format | What it does for a human reader | What it does for AI search |
|---|---|---|
| Long narrative guide | Builds trust if a client reads the whole thing | Rarely gets lifted, the answer is buried mid page |
| FAQ style page | Answers the exact question fast | Gets pulled directly into AI Overview and ChatGPT answers |
| Blog post with a long introduction | Reads well to a traditional SEO checklist | The model cannot find where the actual claim starts |
4. You Do Not Have to Choose One
The long guide is not wasted. Keep it for the reader who wants depth and for traditional search ranking. Add a short FAQ block near the top of that same page, written in plain question and answer pairs that cover what clients actually ask. One page then serves both audiences instead of the team publishing twice for no extra return.
A model does not reward the effort that went into a page. It rewards the sentence it can lift cleanly and use on its own.
Fewer Words, Answered Better, Wins the Citation
Depth still matters for the client who reads to the end. It does nothing for the client who never reaches your site at all because an AI assistant answered the question for them using someone else's page. Firms that win both keep the long form content and build a second, shorter layer written specifically to be quoted.