SEO + AI for Pages and Blog Posts

The page and blog editors provide a separate SEO + AI workflow alongside their original AI controls. Use it to review a brief, keywords, available Search Console evidence and a localized URL before generating a preview.

Before you start

Open a custom page or blog editor with the appropriate permission. Enter the current title and content. Prepare accurate business facts, audience, purpose, products/services and desired sections. Do not put passwords or private customer data in the brief.

This pilot reads the editor's current content and the additional brief. It differs from Product SEO + AI, which uses saved product information.

Suggest keywords and URL

1. Open SEO + AI from the editor.
2. Check the source title and enter a specific content brief. The button requires a title of at least two characters and a brief of at least ten characters.
3. Choose the content and URL language.
4. Click Suggest keywords & URL and wait for the proposal.
5. Read the suggested primary keyword, supporting phrases, URL and explanation.
6. Review competing SEO targets and the Search Console evidence status before accepting.

The pilot checks existing SEO records to identify competing primary targets. Prefer a distinct primary phrase reflecting this page's purpose. Shared supporting phrases are allowed; avoid changing a factual brand or product name simply to make every word unique.

Changing the title, brief or language resets the proposal. Changing a proposed keyword or slug requires a new preview; an old preview is not the updated brief.

Use Search Console evidence correctly

Connect the intended site in Search Console. The proposal shows its available evidence status, period, queries, pages, clicks and impressions. Check any limited-data notice.

Disconnected, unavailable or empty data does not mean zero search demand. These are your site's observed queries, not general market search volume. When no usable evidence exists, facts-based keyword suggestions remain suggestions, not measured popularity or promised rankings.

Generate and inspect the preview

1. Edit the primary phrase, supporting phrases and proposed URL as needed.
2. Click Approve brief & generate preview.
3. Review the SEO title, meta description, proposed/existing URL and body. A blog preview can also include an excerpt.
4. Check facts against your brief, remove unsupported claims and inspect headings, links and tables.
5. If the brief is wrong, correct it and generate a new preview rather than publishing unsuitable text.

The page title provides the main heading. Organize body sections with H2 and subsections with H3; use H4 only for a genuine deeper level. Do not repeat headings just to insert keywords. Preserve correct brand/model names in localized URLs. Existing slugs shown by the pilot are preserved; do not assume its proposal silently renames a live URL.

Apply, save and publish are different

Click the preview's Apply action to return the results to the page/blog editor draft. Unlike the product pilot's direct Save & apply, this action does not finish saving the page or post.

Review the populated editor and use Save, Save Draft or Publish, as appropriate. Reopen the saved record and check its content, metadata and status. Closing the editor without saving can lose applied changes.

A published page/post is still private if its storefront has not been published. Custom-domain verification, active SSL and explicit site publication are separate requirements.

Credits and recovery

Successful suggestions and newly generated previews consume the generation credits described in the dialog. Applying an existing preview does not generate it again. Check the displayed allowance before repeated suggestions.

If Suggest is disabled, check the title/brief lengths and initial context load. For connection or provider errors, preserve your draft and read the error before retrying. For an expired preview, reopen and prepare a fresh one. If content appears unchanged after Apply, inspect the parent editor, then save and reopen it; a custom visual layout can be separate from ordinary body content.

See SEO Settings, Custom Pages, Blog and Visual Editor. Generation is not a guarantee of indexing, ranking or inclusion in AI answers.