# Automate SEO drafts with an editor review

> Use Search Console data to choose pages, save suggested changes as drafts and check them before publishing.

Source: https://fullbytedeveloper.com/blog/automate-seo-with-editor-review
Keyword: AUTOSEO
Published: 2026-11-05

Automate the collection and drafting work, then keep a person responsible for the published page. Google asks publishers to verify AI-generated content, including metadata. Its spam policy targets scaled content made to manipulate rankings without helping users. [1][2]

## Pick pages from search data

Search Console's `searchAnalytics.query` returns clicks, impressions, click-through rate and position. It supports page and query dimensions and requires authorization and a date range. The API returns top rows rather than guaranteeing every row. [3]

Look for pages with meaningful impressions and few clicks. Read the queries and the page before deciding whether a title change would help. Low click-through rate alone does not explain why a result was skipped.

## Prepare an editing brief

Supply the page, its audience, the search queries and sources the draft may cite. Ask for suggested changes to the title, description and outline, with a separate list of claims to verify.

Check the draft against those sources and the actual product. Include metadata in that review, as Google's guidance recommends. [1]

## Save a WordPress draft

The WordPress API documents creating and updating posts, including a `status` value of `draft`. Use the post ID when updating an existing post and confirm that it belongs to the intended page. [4]

Preview the draft before publishing. Review links, headings and the rendered page as well as the text.

## Check the resulting page

Lighthouse CI documents collecting audits and applying assertions in a build workflow. Follow its setup guide for the site's build and serving configuration before using its autorun command. [5]

```bash
lhci autorun
```

Use these checks to catch page regressions. They do not prove a ranking improvement. Keep the original metrics and compare later Search Console data over a comparable period. [3][5]

## Sources

1. [Google guidance on generative AI content](https://developers.google.com/search/docs/fundamentals/using-gen-ai-content)
2. [Google spam policies](https://developers.google.com/search/docs/essentials/spam-policies)
3. [Search Console Search Analytics query](https://developers.google.com/webmaster-tools/v1/searchanalytics/query)
4. [WordPress posts REST API](https://developer.wordpress.org/rest-api/reference/posts/)
5. [Lighthouse CI getting started](https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/getting-started.md)

## Original posts

- [Instagram reel](https://www.instagram.com/reel/DfFHm5HmB6s/)
- [Facebook reel](https://www.facebook.com/reel/2141697553143644)
- [Threads post](https://www.threads.com/@fullbytedeveloper/post/DfFHlYTE6kg)
- [TikTok video](https://www.tiktok.com/@fullbytedeveloper/video/7702081837979421959)