TL;DR — The quick version
Enter your Sitecore site URL → AI rewrites every page title, meta description and slug → download the Sitecore JSON → run the included PowerShell Extensions script in Sitecore to apply all changes in bulk.
Who this is for
- Sitecore developers
- Digital experience teams
- Enterprise marketing teams
- Sitecore implementation partners
What you get with the Sitecore export
Platform-specific SEO metadata and implementation guidance for Sitecore, using the safest supported route rather than forcing a generic bulk import.
Content-safe by design
The exporter is designed not to overwrite page-body content, product descriptions, prices, inventory, images or publication state. Original and recommended SEO values remain separate, and automated regression tests guard against destructive fields being added to exports.
- JSON export formatted for Sitecore PowerShell Extensions (SPE)
- Included C# snippet for Sitecore Content Delivery API updates
- Updates Page Title, Browser Title, Meta Description and NavigationTitle fields
- Compatible with Sitecore XM, XP and XM Cloud
- Handles both SXA and non-SXA implementations
The payoff
What changes when your Sitecore metadata targets the right traffic
This is not about writing prettier titles. It is about attracting the visitors who are ready to buy — and doing it at a fraction of the time and cost of doing it manually.
A full metadata rework that would take a content team 40+ hours of manual writing is done in under 10 minutes. Review, approve, export, import.
Every title and meta description is rewritten for the search intent behind the query — transactional, commercial, informational. You attract buyers, not browsers.
Better metadata means better rankings, higher click-through rates and more qualified visitors. That compounds month after month — not a one-off spike.
Original and recommended values stay separate so you can review page-level changes before they are implemented in the website platform.
Step-by-step guide
How to fix your Sitecore SEO metadata
Run the audit on your Sitecore site
Enter your Sitecore site URL. We crawl every page, landing page and content item — up to 1,000 URLs.
Review and approve
AI rewrites every page title and meta description for search intent. Edit inline and approve the rows you want to export.
Download the Sitecore JSON
Click the Sitecore JSON export tile. You get a structured JSON array with optimised Title, BrowserTitle, MetaDescription and Slug for each item.
Open Sitecore PowerShell ISE
In Sitecore, go to Development Tools → PowerShell ISE (or PowerShell Console). You must have Sitecore PowerShell Extensions (SPE) installed.
Run the SPE import script
Paste the included PowerShell script into the ISE, point it at your JSON file path, and run. The script iterates each item by URL, finds the Sitecore item, and updates the SEO fields.
Publish items
After the script runs, publish the updated items from the Sitecore Content Editor or via SPE bulk publish. Changes will be live once published to your CD environment.
Important: If you change any URL slugs or handles, set up 301 redirects from the old URLs to the new ones before or immediately after importing. This protects your existing search rankings and any backlinks pointing to the old addresses.
Choose your tier
Sitecore SEO audit, seven tiers from £29
One payment. Every page on your Sitecore site audited, rewritten and export-ready. No subscription, no lock-in, no recurring fees.
Choose the audit that fits your site.
This is an AI-native audit by Digital Womble, the original authority in search. Every page is read, scored for search intent, and rewritten for the terms buyers actually search.
Every tier includes
- AI-rewritten titles and meta descriptions for every page
- Platform-specific export or implementation file with guided steps
- Search intent classification per page
- Focus keyword, slug and redirect map included
- Broken link report with fix suggestions
Common questions
Sitecore SEO — frequently asked questions
Scan your Sitecore site with the Website Optimisation tool, review the recommended titles and meta descriptions, then use the platform-specific export or implementation worksheet. Where a safe native import is available, the instructions identify it; otherwise current and recommended fields stay separate for controlled implementation.
The tool is designed to reduce manual work, but the safest implementation route depends on the Sitecore content type and available identifiers. the On-Page SEO Tool separates current and recommended values and provides platform-specific instructions rather than claiming every CMS supports the same bulk-import workflow.
A one-off scan starts at £29 for up to 100 pages and covers up to 15,000 pages at the top tier. The price is shown before checkout, with no subscription required.
the On-Page SEO Tool makes titles and descriptions clearer and more intent-aligned, which can help search and AI systems interpret page purpose. It does not guarantee rankings, AI citations or inclusion in Google AI Overviews.
The Sitecore export is designed to preserve existing website content and functionality. It does not intentionally carry page-body content, commerce data or publication controls that could overwrite the live site. Original and recommended SEO values remain separate, and destructive-field regression tests protect the export format. Review the supplied platform instructions before implementation, especially for URL changes and redirects.
Yes. SPE is required to run the import script. It is available free from the Sitecore Marketplace and is standard on most Sitecore implementations.
Yes. For XM Cloud, use the Content Management API or the Pages editor to update items. The JSON export provides all the data you need for either approach.
The script updates the Page Title, Browser Title, Meta Description and NavigationTitle fields. For SXA sites, it also updates the Navigation Title field in the page metadata section.
No. Only the SEO metadata fields are updated. All page content, components, datasources and rendering parameters remain completely unchanged.
The JSON is grouped by URL path. For multisite setups, run the script per site root. The script can be filtered by site root path to avoid cross-site updates.