ZEISMO SEO
Browse guides

Guide 04

Look after your site

Run a local audit, review SEO history, and use redirects, broken links, competitors and performance checks.

ZEISMO SEO 1.2.1Step-by-step tutorial

Audit saved SEO data

Site Audit: scan controls, saved coverage and indexability guidance.
Site Audit: scan controls, saved coverage and indexability guidance. Actual v1.0.3 sandbox screen; test data is not customer results.
  1. Start a new scan.

    Open Site audit, choose the content age threshold and select Start a new scan. Each batch reviews up to 25 published, unprotected pages.

  2. Let batches finish or continue manually.

    The running indicator shows active work. WordPress scheduled tasks can continue the scan, and Continue next batch is available when you want to advance it yourself.

  3. Review the scope.

    The audit reads saved SEO fields, content age and links in stored HTML. It does not render page-builder output, measure rankings or confirm search-engine indexing.

  4. Fix and rescan.

    Open the relevant page or setting, save the change and run a new scan when you need refreshed results.

Review metadata history and undo safely

SEO change history: saved ZEISMO metadata revisions and recovery actions.
SEO change history: saved ZEISMO metadata revisions and recovery actions. Actual v1.0.3 sandbox screen; test data is not customer results.
  1. Open Change history.

    Use the ZEISMO SEO menu or the Site Audit link. History starts with version 1.0.3 and records per-page SEO metadata saved through ZEISMO.

  2. Compare the saved values.

    Review the editor, source, time, and before and after values before restoring anything.

  3. Undo only the latest matching revision.

    The conflict check stops an undo when newer metadata is present. Reload and review rather than overwriting a later edit.

Read dashboard notifications

Notifications: supported task completions and actionable site notes.
Notifications: supported task completions and actionable site notes. Actual v1.0.3 sandbox screen; test data is not customer results.

Open Notifications from the ZEISMO dashboard. New items describe supported background completions and site notes. Open the relevant action, then dismiss an item when you no longer need it.

Fix an old URL with a redirect

Redirects & 404s: add a rule and review recorded missing URLs.
Redirects & 404s: add a rule and review recorded missing URLs. Actual v1.0.3 sandbox screen; test data is not customer results.
  1. Find the URL that needs fixing.

    Open Redirects & 404s. You can enter an old path directly, or choose Create redirect from a recorded 404.

  2. Choose the destination and response.

    For a permanent move, choose 301 and enter the replacement URL. Use 302 for a temporary move. Choose 410 only when content is intentionally gone; it is not a redirect to another page.

  3. Add the rule.

    Check that the old URL and destination are different, then select the add button. The rule takes effect when saved.

  4. Test as a visitor.

    Open the old URL in a private browser window. Confirm that it reaches the intended page without looping.

Check your result: The old path sends visitors to the intended destination. A saved rule alone is not proof that the destination is correct.

Move from another SEO plugin safely

  1. Back up the site.

    Keep a complete database and file backup. A selected SEO checkpoint is not a full-site backup.

  2. Preview supported metadata.

    Open Migrations, choose the installed source plugin and prepare a preview. Supported fields from Yoast SEO, Rank Math and All in One SEO are mapped for review. Unsupported template variables are skipped.

  3. Select changes deliberately.

    Review source and destination values. Select only changes you want; existing handwritten values are protected unless you explicitly choose replacement. Changed sources are checked again when applying.

  4. Verify output.

    Inspect representative public pages and sitemaps before deactivating the previous plugin. The migration does not delete its original records. Keep one plugin responsible for overlapping SEO output.

Review selected content edits

Content tools start with a reviewed preview.
Content tools start with a reviewed preview. Actual v1.2.0 sandbox screen; test data is not customer results.

Open Content tools, select the supported operation and prepare a preview. Review rows before applying. A stale source is skipped instead of silently overwriting a newer edit. Link and image changes have bounded supported formats; inspect the resulting page.

Create a selected SEO checkpoint

Checkpoints protect selected supported records.
Checkpoints protect selected supported records. Actual v1.2.0 sandbox screen; test data is not customer results.

Select supported records and give the checkpoint a useful name. Review its contents before restoring. Restore creates a new reviewed change rather than replacing your database. Up to 20 named checkpoints and 50 selected records per checkpoint are supported.

Compare on-page content

Competitors: saved domains and the keyword selector.
Competitors: saved domains and the keyword selector. Actual v1.0.3 sandbox screen; test data is not customer results.
  1. Set a focus keyword on one of your pages.

    Save the page so its keyword can appear in the comparison selector.

  2. Save competitor domains.

    Open Competitors, enter the relevant domains and select Save competitors. Your plan and distribution determine the available limit.

  3. Choose a keyword and compare.

    Select a keyword and press Compare. Review the returned page and its measured content signals before deciding what to improve.

Read a ZEISMO performance check

Performance: the saved ZEISMO diagnostic result for the sandbox homepage.
Performance: the saved ZEISMO diagnostic result for the sandbox homepage. Actual v1.0.3 sandbox screen; test data is not customer results.
  1. Confirm the feature is available.

    Open Performance. The screen explains if an account connection or eligible plan is required.

  2. Select Check now.

    ZEISMO fetches your homepage from its own servers. The check uses the task allowance described by the screen.

  3. Read the timestamp and measurements.

    Review server response time, HTML download time and size, plus the reported script, stylesheet and image counts.

  4. Review recommendations before making changes.

    Apply appropriate changes through your normal site workflow, then run a new check to compare.