Schema Markup Validator
Check JSON-LD for syntax errors and missing required fields.
Build nginx rewrite and return rules from a redirect map.
The Nginx Redirect Generator writes redirect configuration in the three shapes nginx supports — individual location blocks, return directives, and a map block — and recommends which to use based on how many redirects you have. Past about twenty, a map is the only sensible option, because location blocks are checked in order on every request.
Paste your redirect map and the generator writes nginx configuration in whichever of the three shapes fits: individual location blocks for a handful of redirects, return directives inside a server block, or a map block for hundreds.
The map block is the one worth knowing about. nginx evaluates location blocks in order, so a configuration with five hundred of them is slow on every request, not just the redirected ones. A map is a hash lookup: it is compiled once at startup and costs the same whether it holds ten entries or fifty thousand. Past about twenty redirects it is the only sensible choice, and the generator switches to recommending it automatically. It also reminds you that a map block goes in the http context, not inside server, which is where most first attempts fail to start.
A hash lookup compiled once at startup, costing the same at ten entries or fifty thousand.
A map goes in http, not server. That single fact is why most first attempts fail to start.
Location, return and map, from the same input, so you can see what each looks like.
The same flattening and loop detection as the Apache generator.
It tells you to run nginx -t first, because a syntax error on restart takes the server down.
One per line as "old path, new URL". Full URLs are reduced to paths where they need to be.
Location blocks, return rules or a map block. The tool recommends one based on how many you have.
A map block goes in the http context; location and return go inside the server block.
Run nginx -t first. A syntax error there takes the whole server down rather than one rule.
Past about twenty redirects. nginx checks location blocks in order on every single request, so a long list slows everything down. A map is a hash lookup compiled once at startup, and it costs the same at ten entries or fifty thousand.
In the http context, outside and above your server blocks — usually in nginx.conf or an included file. Putting it inside a server block is a configuration error and nginx will refuse to start, which is the most common first mistake with maps.
return, almost always. It is faster and its intent is obvious. rewrite is for cases where you need to capture part of the URL and reuse it in the destination. Using rewrite for a simple redirect works but is slower and harder to read.
A reload is enough and it is graceful — nginx -s reload, or systemctl reload nginx. Always run nginx -t first: a syntax error in a reload is survivable, but the same error on a restart leaves the server down.
What people who use the Nginx Redirect Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Nginx Redirect Generator. It takes half a minute and no account.
Write the first reviewCheck JSON-LD for syntax errors and missing required fields.
Check where a keyword appears on a page, not just how often.
Break any URL into its parts, query string included.
Weigh a page's HTML and see what is taking up the room.
Build the hreflang set for a page, with return links checked.
Compress a stylesheet without touching what it means.
Cluster a keyword list into groups by the words they share.
Deduplicate, trim and tidy a messy keyword export.