How we write and publish
a blog post. Properly.

Open the Blog Topics list. Pick a topic that's been agreed with Rachel and is next in the queue. Check if it's a Founder (F) or Agency (A) audience post.

Update the status column to "Drafting" and add today's date. This stops anything getting lost month-to-month.

Each post needs 1 primary keyword plus 3-5 secondary keywords.

• Primary: the exact phrase someone would Google. Goes in title, first 100 words, one subheading, meta description.
• Secondary: 3-5 supporting phrases including Reddit language (audience fatigue, pause losers, ROAS dropped).

Write these into your draft doc before you start. Locking them in now prevents rework later.

Open the Competitors & Inspiration doc. Skim how others frame the same topic. The goal isn't to copy. It's to find an angle they're missing or doing badly. That's where The Peach System's edge sits: real ad-account experience.

Open Claude.ai in a new tab. Start a new chat. Paste in:

• Your topic
• The audience (F or A)
• Your primary keyword and 3-5 secondary keywords
• A link to the Ramadan post as the style reference
• A request for a 1,200-1,800 word draft with question-based section headings

Ask Claude to: include the primary keyword in the title, first 100 words, one subheading, and meta description. Cite stats with named sources only. End with a soft connection to The Peach System or The Digital Peach, no hard sell.

Read what Claude returns. Ask for specific improvements:

• "Tighten the opening, it's too generic"
• "Suggest 3 alternative headlines under 70 characters"
• "Remove any statistics that aren't from a named source"
• "This paragraph feels textbook, make it feel like real ad-account experience"

Copy Claude's draft into a new Google Doc. This is where the real value-add happens. Work through it section by section.

• Replace generic statements with specific examples from real ad accounts
• Apply UK English spelling (optimisation, personalised, behaviour, colour)
• Remove any em dashes
• Strip italics from body copy
• Add Rachel's voice: direct, practical, written from inside live ad accounts
• Keep technical accuracy where Claude got it right, don't rewrite for the sake of it

Share the doc with comment access. Tag Rachel in Slack or email with:

• Link to the doc
• Topic, primary keyword, audience (F or A)
• Specific questions you want her input on

Rachel reviews and leaves inline comments. Default to async. No meeting unless something significant needs discussing.

Address each comment. If something is unclear, ask in the comment thread before guessing. Resolve comments as you go so Rachel can see what's done.

One careful read-through. Check:

• Spelling and grammar
• Sentences that run too long or repeat themselves
• UK English consistency
• No em dashes
• No italics in body
• Primary keyword in title, first 100 words, and at least one subheading
• Word count between 1,200 and 1,800

Find or create a cover image. Ideal: 1200x630 px, JPG or PNG, under 500KB.

• Open the Cloudflare R2 dashboard
• Navigate to the blog-post-images folder
• Upload with a lowercase, hyphenated filename (no spaces, no apostrophes)
• Copy the public URL: https://pub-55dc34ad0599416491f4a8065aa34c72.r2.dev/blog-post-images/your-image.jpg
• Save it for the next step

Open a new Claude.ai chat. Click "Copy prompt" below, paste it into Claude, replace [PASTE THE DRAFT HERE] with your finished Google Doc content, and send.

Claude returns formatted markdown with frontmatter, headings, and house style applied. Fill in any placeholders (cover image URL, alt text, category, date).

You are helping convert a finished blog post into a markdown file for The Peach System Blog. The Peach System is The Digital Peach's Meta Ads intelligence platform, serving e-commerce brands and agencies in the UAE and globally.

Use this exact frontmatter structure at the top:

---
title: "Headline under 70 characters, include year and location where relevant"
description: "150-220 characters. Front-load keywords in the first 155 characters since Google truncates the rest in SERPs"
publishDate: YYYY-MM-DD
updatedDate: YYYY-MM-DD  (only include if the draft mentions being revised)
author: "Rachel Lindsay"
category: "Choose ONE: Meta Ads, Attribution, Creative Strategy, Agency Ops, CRO, UAE Market"
readTime: "X min read"  (calculate as word_count / 200, rounded up)
coverImage: "https://pub-55dc34ad0599416491f4a8065aa34c72.r2.dev/blog-post-images/[filename]"
coverAlt: "Describe the image with relevant keywords"
featured: false
draft: true
keywords: ["keyword one", "keyword two", "keyword three", "keyword four", "keyword five"]  (5-7 keywords, mix of head terms and long-tail)
---

STYLE RULES:
- No em dashes. Use commas, full stops, or spaced hyphens ( - ).
- No italics in body copy. Italics allowed only in the footer attribution line.
- No fabricated metrics or testimonials. If the draft cites a statistic without a clear named source, flag with [SOURCE NEEDED] rather than inventing one.
- UK English spelling: optimisation, personalised, behaviour, colour, organise, realise. Reject US spellings even if grammar tools suggest them.
- Mostly 2-4 sentence paragraphs. Use single-sentence paragraphs sparingly for emphasis.
- Use ## for main section headings, ### for sub-headings (rarely needed).
- Section headings should be question-based ("What happens to Meta ad costs during Ramadan?") or imperative ("Get your tracking right", "Plan for Eid now"). Keyword-rich.
- Bold key statistics in the body so they stand out.
- Cite statistics inline: "According to [Source name], [statistic]." Include hyperlinks to sources where URLs are available, otherwise flag with [LINK NEEDED].
- Use bulleted lists for thematic groupings (e.g. creative themes, audience segments).
- Body length: 1200-2000 words. Flag if the draft falls outside this range.

VOICE:
- First person plural ("we'd do", "we check", "in our experience").
- Direct, practical, from inside live ad accounts.
- Confident but warm. No jargon for jargon's sake.

SELF-PROMOTION:
- Mention The Peach System or The Digital Peach 2-3 times maximum, only where it adds genuine context.
- Link "The Peach System" to https://thepeachsystem.com on first mention.
- No hard sell.

CLOSING:
- Soft close, not a CTA. A playful tagline or seasonal greeting is fine where appropriate.
- End the body, then a horizontal rule (---), then a single-line italicised footer like:
  *Published by The Digital Peach, a Meta Business Partner agency in Dubai. The Peach System is The Digital Peach's Meta Ads intelligence platform...*

REFERENCE POST: The Ramadan Meta Ads post at https://blog.thepeachsystem.com/ramadan-meta-ads-uae is the tone and structure to match.

WHAT TO DO:
1. Read the draft below.
2. Generate frontmatter. Leave [PLACEHOLDER] where info is missing.
3. Format the body using markdown per the rules above.
4. Do not change the substance. Only format and polish.
5. Hyperlink all named sources where URLs are obvious. Flag [LINK NEEDED] if unsure.
6. Bold all statistics with named sources.
7. Suggest a filename for the markdown file in the format `slug-name.md` - lowercase, hyphens between words, under 60 characters, includes the main keyword. Put this on a line at the very top of your response like: `Filename: slug-name.md`
8. Return the complete markdown file ready to paste into GitHub.

NOW CONVERT THE FOLLOWING DRAFT INTO MARKDOWN:

[PASTE THE DRAFT HERE]

Before you save the markdown file or send it to Rachel, scan the entire output for any of these tags:

• [SOURCE NEEDED] - a statistic Claude could not verify. Either find a real, named source and add it inline ("According to [Source], [stat]") or cut the sentence entirely.
• [LINK NEEDED] - a citation that needs a hyperlink. Find the source URL and add it, or cut.
• [PLACEHOLDER] - missing frontmatter info (publishDate, coverImage filename, etc.). Fill it in.

Once every tag is resolved, you are ready for Phase 7.

Send Rachel a message containing:

• The complete markdown file (paste directly or attach as .md)
• Suggested filename in lowercase-with-hyphens.md format
• The R2 link to your cover image
• Any notes (time-sensitive content, specific publish date, etc.)

Update the Blog Topics sheet: change status from "Drafting" to "With Rachel" and add the Google Doc link in notes.

Rachel commits to GitHub and publishes. Cloudflare auto-deploys. Post is live in 2-3 minutes. Rachel updates status to "Published" with the live URL.