Skip to content

Catalog

SEO policy templates

Create reusable SEO rules and inspect product SEO output.

For workspace users and administrators · Updated October 1, 2026

What this module is for

Create reusable SEO rules and inspect product SEO output.

Use this page when you need to complete the task yourself and understand what each action changes. The steps name the relevant screen, explain why the action belongs in the workflow, and state what to verify before moving on.

Before you start

  • Sign in with a role that can view or change the records in this guide.
  • Have the product, file, channel, or workspace information ready before starting an action that saves data.
  • Use a small test record or file first when an action affects multiple products or a connected channel.

1. Set a policy

Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.

  1. Step 1.1

    Do this: Open SEO Policies and choose Create Policy.

    Why this matters: This keeps the set a policy work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.

  2. Step 1.2

    Do this: Use the policy form to define the template and fields your products should follow.

    Why this matters: This keeps the set a policy work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.

  3. Step 1.3

    Do this: Save the policy and review it from the list before applying it operationally.

    Why this matters: This keeps the set a policy work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.

2. Check a product’s SEO workspace

Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.

  1. Step 2.1

    Do this: Open the product’s SEO tab and review the title, description, and saved SEO baseline.

    Why this matters: This keeps the check a product’s seo workspace work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.

  2. Step 2.2

    Do this: Inspect International SEO for hreflang regions and SEO QA & Localization Checks for market-specific problems.

    Why this matters: This keeps the check a product’s seo workspace work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.

  3. Step 2.3

    Do this: Use Internal Link Intelligence to rescan or insert suggested links only after reviewing relevance.

    Why this matters: This keeps the check a product’s seo workspace work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.

3. Audit and improve

Complete these actions in order. They describe the screen to use, the decision to make, and the evidence to check before you move to the next stage.

  1. Step 3.1

    Do this: Use Run Audit and the SEO Review Hub to inspect recommendations.

    Why this matters: This keeps the audit and improve work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.

  2. Step 3.2

    Do this: Open View Performance Report or the product SEO report to review quality distribution and specific issues.

    Why this matters: This keeps the audit and improve work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Confirm that the named screen or panel is visible and contains the expected values. If a control is missing, check your workspace role before continuing.

  3. Step 3.3

    Do this: Correct missing or duplicate content, save, then run the audit again. Use SEO Experiments only with a defined comparison goal.

    Why this matters: This keeps the audit and improve work traceable and makes the next review, validation, or handoff easier to complete.

    Check before continuing: Look for a confirmation message, a newly created record, or a job status entry. If nothing changes, read the inline field error or job detail before retrying.

Events and statuses to watch

Actions such as saving, importing, exporting, connecting, publishing, and approving can either update a record immediately or create background work. Wait for the on-screen confirmation and then check the relevant list, detail view, or job status before repeating an action.

  • Saved or created: confirm the record appears with the intended values.
  • Queued, running, or processing: wait for completion and open the job or event detail if progress stops.
  • Failed, partial, rejected, or blocked: read the specific message, correct the source data or permissions, then retry only the affected work.

Continue with a related guide