How do I publish SEO pages and blog posts with Claude Code without hurting my site?

Let Claude Code add new pages only, never edit the ones that already work, and check every page on the live site after the deploy. Write the rules in CLAUDE.md, work on a branch, review the facts yourself, and publish in small batches of pages that each answer one real buyer question. Google treats mass pages without added value as spam.

Facts

Google's spam policies, updated August 28, 2026, list using generative AI to generate many pages without adding value for users as scaled content abuse. (Google Search Central: Spam policies (scaled content abuse))
Google's guidance on generative AI content, updated October 1, 2026, says to fact-check and review AI-generated content before publishing, including titles, meta descriptions and alt text. (Google Search Central: Guidance on using generative AI content)
Claude Code loads the project's CLAUDE.md at the start of every session, and its docs recommend keeping each file under 200 lines. (Claude Code docs: How Claude remembers your project)
Claude Code's docs say CLAUDE.md is context, not enforced configuration; to block an action regardless of what Claude decides, use a PreToolUse hook. (Claude Code docs: How Claude remembers your project)
Google uses a sitemap's lastmod only when it is consistently and verifiably accurate, and it should reflect the page's last significant update. (Google Search Central: Build and submit a sitemap)

What can go wrong when Claude Code writes my blog posts?

Most damage comes from edits the agent was never asked to make, not from the new post itself:

It rewrites a layout, the navigation or a page that already ranks
It publishes many similar pages that add nothing, which Google calls scaled content abuse
It states a price, a number or a customer it did not check
It marks every page as updated in the sitemap, so lastmod stops being trusted

How do I stop Claude Code from touching pages that already work?

Write the limit in CLAUDE.md and back it with a hook. CLAUDE.md is read in every session but is guidance; a PreToolUse hook can refuse edits outside the content folder. Work on a branch and read the diff before merging: a new post should only add files.

# CLAUDE.md: content rules
- Add posts only as new files in content/blog/. Never edit existing pages,
  layouts, navigation or the home page.
- One buyer question per post: the title is the question,
  the first sentence answers it.
- Every number links to its source. No invented customers, quotes or figures.
- Add each new post to the sitemap; change lastmod only on pages you changed.
- Run the build and work on a branch; never push to main.

What should each new blog post include?

Each post answers one question a buyer actually asks, and nothing on it needs the rest of the site to make sense:

The question as the title and H1, in the buyer's own words
The answer in the first sentence, then the details
Facts with a date or number and a link to the source that states it
A meta description, the publish date and links to related pages
An entry in the sitemap with an accurate lastmod

How do I choose what Claude Code should write about?

Start from your buyers, not from a keyword list. Write down who buys, the situations they search in and the questions they ask an AI assistant or a forum, then group them by situation. The first batch covers the situation you are most likely to win.

How do I check a post after the deploy?

Open the live address the way a crawler does, without running JavaScript, and confirm the title, the answer and the facts are in the HTML. Then check that the page is in the sitemap and ask Search Console to inspect the URL.

Step by step

Write the rules. Put the content rules in CLAUDE.md: new files only, one question per post, sources for every fact.
Add a guard. Ask Claude Code to add a PreToolUse hook that blocks edits outside the content folder.
Draft a small batch. Have it write a handful of posts on a branch, each answering one buyer question.
Review before merging. Check the facts yourself and confirm the diff only adds files and sitemap entries.
Check the live pages. After the deploy, read each page's raw HTML, confirm the sitemap and inspect the URLs in Search Console.

Common mistakes

Asking for 100 posts at once from a keyword list instead of a few that answer real buyer questions.
Letting the agent "improve" existing pages while it adds new ones.
Trusting the agent's summary that the post is live without opening the live page.
Publishing numbers and prices nobody checked against a source.

How easyIndex solves it

easyIndex gives Claude Code the method over MCP, one step at a time with the current rules: who buys, what they ask, and batches you approve before anything is published. Claude Code writes every page in your repo; easyIndex never touches your site. It audits each page when submitted, checks it on the live site after publishing, and a step completes only on that evidence, not on the agent's report. US$ 30 per website a month, with a 7-day free trial.

Frequently asked questions

Does Google penalize blog posts written with Claude Code?

Google's policies target pages made mainly to manipulate rankings without adding value, however they are written. A reviewed page that answers a real question is not that.

Should Claude Code publish straight to main?

Better not. A branch and a preview deploy let you read the diff and the pages before they go live.

Do I need a CMS for this?

No. If your site is in a repository, posts can be Markdown or MDX files that Claude Code adds and your build turns into pages.

How many posts should I publish at once?

A batch you can review yourself. Quality and the right questions matter more than volume.

Continue reading

Last verified on October 13, 2026.