> **Note:** How to use this template: replace everything in [square brackets]. The notes explain what goes into each section and why. Delete them before you publish. The order follows what readers, Google and AI answers all need: the answer first, then the details, and at the end the evidence and who stands behind it. **Editorial brief (do not publish)** | Field | Entry | Note | |---|---|---| | Primary keyword | [e.g. how to store coffee beans] | The one search query this post answers. One page per topic. | | Secondary keywords | [2–5 related terms and questions] | From “People also ask”, Search Console or Keyword Planner. Not every variation needs its own section. | | Search volume / mo | [number, source, date] | Helps you prioritize, not write. | | Search intent | [informational / commercial / transactional / navigational] | What does the searcher want to do next? That decides the format. | | Target URL | [/blog/short-slug] | Short, no date, with the primary keyword. | | Title tag | [about 50–60 characters] | Unique, descriptive, concise. Google sets no fixed limit but truncates to fit the screen. | | Meta description | [about 120–155 characters] | Sums up what the page offers. No fixed limit either; Google truncates as needed. | | Author | [name, role] | Who wrote this, and why do they know? | | Expert review | [name, date] | Optional. Worth it for health, legal and financial topics. | | Published on | [Month D, YYYY] | | | Internal links | [3–5 relevant pages of your own] | Plus 1–2 existing pages that link to this post. | | Call to action | [What should the reader do next?] | One goal per post. | # [H1: the question or the promise, with the primary keyword] > **Note:** One H1 per post. It picks up the search query and says what the reader gets, e.g. “How to Store Coffee Beans: Jar, Fridge or Freezer?”. Only add a year if you also update the post every year. By [author], [role] · Last updated: [Month D, YYYY] > **Note:** Who wrote it, and how current is it? Google recommends bylines where readers expect them and a visible, labeled date such as “Published” or “Last updated”. **[Short answer: 2–4 sentences that answer the question in the H1 directly. The first sentence is the answer, not a lead-in. Include the most important number or condition.]** > **Note:** The most important paragraph. Someone who reads only this has the answer. A paragraph that makes sense on its own also works as an excerpt, for example in a search result or an AI answer. Example: “Store coffee beans airtight, dark and cool in a canister, not in the fridge. …” Key takeaways: - [Takeaway 1, with number and source] - [Takeaway 2] - [Takeaway 3] > **Note:** 3–5 bullet points for skimmers. Only statements the post backs up. Contents: 1. [Section 1] 2. [Section 2] 3. [Section 3] 4. FAQ > **Note:** Worth it for long posts. Each item jumps to its subheading via an anchor link. ## [What is …? / What this is about] [The first sentence answers the heading. Then explanation, example, distinction.] > **Note:** Every subheading is a question readers actually have, or a clear statement. Test: read only the first sentence of each section. Is the answer there? Google recommends paragraphs and sections with headings that give structure. You don’t need to chop content into tiny chunks, and according to Google there is no ideal length. ## [Main part: steps, reasons or options] ### Step 1: [specific action] [What to do, how to tell it worked, the typical mistake.] ### Step 2: [specific action] […] > **Note:** Instructions as numbered steps, decisions as options with pros and cons. One image or video per step where it helps. ## [Comparison or overview] | [Criterion] | [Option A] | [Option B] | [Option C] | |---|---|---|---| | [Price] | [ ] | [ ] | [ ] | | [Feature] | [ ] | [ ] | [ ] | | [Best for] | [ ] | [ ] | [ ] | Source: [publisher, as of Month D, YYYY] > **Note:** Use tables for anything readers compare: prices, features, pros and cons. Put the source and date right below. ## [From our experience: …] [Your own data, your own example, your own photos: something only you have.] > **Note:** The part nobody can copy. Google distinguishes commodity content that anyone could write from content with first-hand experience and expertise, and recommends the latter. Examples: an analysis of real customer questions, your own measurements, photos from your business, a customer case with numbers (only with the customer’s approval). ## [Checklist: the essentials] 1. [Item 1] 2. [Item 2] 3. [Item 3] ## Bottom line: [key message in one sentence] [2–4 sentences: what does this mean for the reader? What is the next step?] [Call to action: product, consultation, download or a related post] Read next: - [Link to a related post] - [Link to a related post] ## FAQ about [topic] ### [Question 1, phrased the way readers ask it?] [2–4 sentences. The first sentence answers the question.] ### [Question 2?] […] ### [Question 3?] […] > **Note:** 4–8 questions the main text hasn’t answered yet, e.g. from Google’s “People also ask” or real customer enquiries. Each answer stands on its own. Google stopped showing FAQ rich results on May 7, 2026. The block is still worth it because it answers questions readers really have. According to Google, no special structured data is needed for the AI features in Google Search. --- About the author: [Name] is [role] at [company] and [experience in 1–2 sentences]. [Link to author page or LinkedIn profile] > **Note:** Google recommends that bylines lead to more information about the author and warns against made-up author profiles. Last updated: [Month D, YYYY]. [Optional: what changed and how often you review the post.] > **Note:** Only change the date when the content has really changed. Google explicitly lists changing the date of pages to make them seem fresh, when the content has not substantially changed, as a warning sign. Sources: 1. [Title], [publisher], [URL], accessed [Month D, YYYY] 2. […] > **Note:** Every number and every checkable claim gets a source, ideally the original (study, authority, manufacturer), not the article quoting it. Link it in the text and collect it here with the access date. --- ## Before you publish - [ ] The short answer answers the H1’s question in its first sentence. - [ ] Every section answers its heading in the first two sentences. - [ ] Your own experience, data or examples are in it. - [ ] Every number has a source with a date. - [ ] Author with role and link; date visible and labeled. - [ ] Title tag and meta description set and unique across the site. - [ ] 3–5 internal links to relevant pages, 1–2 links from existing pages to this one. - [ ] Images have alt text that describes what they show. - [ ] No second page of your own targets the same primary keyword. - [ ] All notes and square brackets from this template deleted. _Sources for the notes (accessed October 8, 2026):_ - [Google Search Central: Creating helpful, reliable, people-first content (Who, How, Why; bylines; no preferred word count; dates only for real changes)](https://developers.google.com/search/docs/fundamentals/creating-helpful-content) - [Google Search Central: Optimizing your website for generative AI features (headings, no chunking, no ideal length, first-hand experience, no special schema)](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide) - [Google Search Central: Influence your byline dates](https://developers.google.com/search/docs/appearance/publication-dates) - [Google Search Central: Title links](https://developers.google.com/search/docs/appearance/title-link) - [Google Search Central: Snippets and meta descriptions](https://developers.google.com/search/docs/appearance/snippet) - [Google Search Central: Documentation updates (FAQ rich results discontinued from May 7, 2026)](https://developers.google.com/search/updates) _Free template by Claire · byclaire.co/templates/blog-post · October 2026 · Free to use and adapt._