URL Rewrite Data for Magento 2 - Headless URLs & Safe Redirect Importer
Perpetual licence — one payment. The version you buy is yours to keep and use for as long as you like, with 12 months of updates and priority support included. When the year ends your store carries on running exactly as it is — only updates and support stop. Renewing is optional, any time: 40% off the list price (not the promotional price). We email you before your licence year ends.
URL Rewrite Data is a Magento 2 module that bundles every product, category, CMS and custom URL rewrite into a JSON snapshot and GraphQL feed, so a headless storefront resolves clean URLs and honours every 301 and 302 redirect at the edge. It also includes a safe, reversible .htaccess redirect importer.
Clean URLs and bullet-proof redirects for a headless Magento 2 store. Bundle every product, category, CMS and custom URL rewrite into one JSON snapshot and GraphQL feed - so an Astro front end resolves the right URL and the right 301/302 at the edge - plus a safe .htaccess redirect importer.
The URL layer headless Magento forgets
When you decouple Magento, its URL rewrites and redirects don't come along for free. URL Rewrite Data exposes them properly: one feed your storefront reads to resolve clean product, category and CMS URLs and honour every 301/302 redirect - at edge speed.
What it does
- Complete rewrite snapshot - products, categories, CMS and custom rewrites in one JSON + GraphQL feed
- Edge-ready redirects - your Astro storefront resolves 301/302s without round-tripping to Magento
- Safe .htaccess importer - bulk-import legacy redirects; it only ever touches its own rows and is fully reversible
- Security-hardened - unsafe targets (javascript:, protocol-relative, off-site) are neutralised to same-site paths
Included in the AgenticEcom Suite
Part of the complete platform - one of 40+ modules in the AgenticEcom Suite.
Frequently asked questions
Why does a headless storefront need this?
Your frontend has to know how to resolve clean URLs to products/categories/pages and honour every 301/302 redirect. The bundle hands it the whole rewrite map (with a version hash) in one call, so it can route and redirect at the edge without querying Magento per request.
Is the .htaccess import safe to run on a live store?
Yes. It previews as a dry run first, only ever writes/updates/deletes rows it owns (htaccess_custom), reports anything that would collide with a real Magento rewrite instead of touching it, and can be fully undone with one click.
What happens to a `javascript:` or `//evil.com` redirect target?
It's forced to a same-site path (e.g. /javascript:…), so it can't act as a script URL or an open-redirect to an external site. Genuine http(s):// targets you intend are kept as-is.
Which .htaccess lines actually get imported?
Only Redirect and RedirectMatch directives with a 301 or 302 status, and only when the path is a literal (regex patterns are flagged for review). Everything else — RewriteRule, IP/country blocks, gzip, comments — is ignored, so pasting a whole file is safe. Verified clean on PHP 8.3, 8.4 and 8.5.
