Website configuration guide: meta tags, robots, sitemaps and CSP

Create a static QR Model 2 code that directly contains your UTF-8 text, with error correction M and a quiet zone of at least four modules. No tracking redirect is added.

Steps

1. Paste content into “Text / URL”, or load the example to try it.
2. Review Image size (pixels), Quiet zone (modules; minimum 4) before selecting “Create QR code”.
3. Review the PNG preview, then download the PNG or SVG file you need.

Available options

Image size (pixels)

256

Every module, including the quiet zone, needs at least 2 pixels. The required size grows with the text and quiet zone.

Quiet zone (modules; minimum 4)

4

Capabilities and limits

• QR Model 2 versions 1–40, correction M, UTF-8 byte mode. Actual capacity depends on encoded bytes. Size 64–2,048 pixels must allow at least 2 pixels per module including the quiet zone; increase size or shorten content when rejected.

Add or replace UTM campaign parameters on an absolute HTTP or HTTPS URL. Existing parameters and fragments remain; blank optional fields leave existing values in place.

Steps

1. Paste content into “URL + parameters”, or load the example to try it.
2. Review Campaign source, Campaign medium, Campaign name before selecting “Build UTM link”.
3. Review the URL result, then use the available copy or download controls.

Available options

Campaign source

Enter as needed

Campaign medium

Enter as needed

Campaign name

Enter as needed

Campaign term (optional)

Enter as needed

Campaign content (optional)

Enter as needed

Capabilities and limits

• Pasted text is limited to 1 MiB; review the result before using it.

Create escaped title, description, canonical and Open Graph HTML tags as copyable text. Add both page and image URLs for the four basic Open Graph properties; platforms decide their actual presentation.

Steps

1. Enter the page title and description in Settings; canonical and sharing image URLs are optional.
2. Review the generated HTML tags; the image URL is not fetched.
3. Copy or download the tags, place them in the page head, and check the published page.

Available options

Page title

Enter as needed

Description

Enter as needed

Canonical URL (optional)

Enter as needed

Open Graph image URL (not fetched)

Enter as needed

Open Graph type

Website · Article

Capabilities and limits

• Input is processed in this browser; unsaved results are lost on refresh.
• A missing page or image URL leaves the basic Open Graph set incomplete.

Generate one robots.txt user-agent group with explicit Allow and Disallow paths and an optional sitemap URL. Robots directives are not access control or secret protection.

Steps

1. Paste content into “Rules”, or load the example to try it.
2. Review User agent, Sitemap URL (optional) before selecting “Generate robots.txt”.
3. Review the Text result, then use the available copy or download controls.

Available options

User agent

*

Sitemap URL (optional)

Enter as needed

Capabilities and limits

• Pasted text is limited to 1 MiB; review the result before using it.

Build XML sitemap entries from a deduplicated list of same-origin HTTP or HTTPS URLs. Last-modified dates are included only when you supply a real date; the site is not crawled.

Steps

1. Paste content into “URL list”, or load the example to try it.
2. Review Actual last-modified date (optional) before selecting “Generate sitemap”.
3. Review the XML result, then use the available copy or download controls.

Available options

Actual last-modified date (optional)

Enter as needed

Capabilities and limits

• Pasted text is limited to 1 MiB and 50,000 nonempty URL lines. Use same-origin HTTP(S) URLs without fragments or credentials. Each normalized, URL-encoded loc must contain fewer than 2,048 characters; Unicode paths may become longer after encoding. One invalid URL rejects the complete output.

Paste the HTML source or <head> tags from a local page to check og:title, og:type, og:image and og:url, then preview the card. You can also draft a card by entering fields manually. No remote page or image is fetched, and platforms may render cards differently.

Steps

1. Keep Paste HTML selected and paste the page source or its <head> tags. You may choose a local image to see the artwork; the og:image URL itself is not fetched.
2. Select Preview share card. Review which Open Graph tags are present, missing, empty or invalid, and check any HTML title or description fallback.
3. For a draft card, change Input method to Enter fields and supply a title and page URL. Review or download the JSON result.

Available options

Input method

Paste HTML tags · Enter preview fields

Preview title

Enter as needed

Preview description

Enter as needed

Page URL (not fetched)

Enter as needed

Capabilities and limits

• Paste up to 1 MiB of HTML. The og:image URL is checked as text and never loaded. An optional local preview image must be a static JPEG, PNG or WebP up to 20 MiB and 16 million pixels.

Inspect an HTTP or HTTPS link before using it: see its destination, path, fragment, and query parameters in order. A fragment written as key=value pairs is decoded separately, including access_token values. The link is never opened.

Steps

1. Paste a full HTTP or HTTPS URL.
2. Check the origin and path, then scan query parameters and any key=value fragment parameters in order. Compare decoded values with encoded text and notice repeated keys.
3. Copy or download the JSON if you need the parsed result elsewhere.

Capabilities and limits

• Only full HTTP/HTTPS URLs are accepted. The parser does not open the link, follow redirects, verify the destination, or determine how a server handles repeated keys.
• Query parameters use form decoding: + becomes a space and %2B becomes +. The path and raw query stay encoded. Username/password values in a URL are omitted from the result.
• Processing stays in your browser. Pasted text is limited to 1 MiB.
• Fragment parameters are included in copied and downloaded JSON. They may contain access tokens; keep the result private. Opaque fragments remain raw text.

Paste HAR JSON or choose one UTF-8 .har/.json export. Review failed requests, status classes and origins, then download the full report. No recorded URL is visited.

Steps

1. Export a HAR from browser developer tools, then select the file or paste its JSON. Only the chosen source is processed.
2. Review request and failure counts, status classes, and the first 50 failed requests.
3. Download the JSON report for all failed requests, origins and the 50 slowest requests. Inspect origins and paths before sharing.

Capabilities and limits

• Pasted HAR text is limited to 1 MiB; one UTF-8 file is limited to 10 MiB and 10,000 entries. Network failures (status 0) and HTTP 4xx/5xx responses count as failed.
• The report excludes URL credentials, queries, fragments, headers, cookies and bodies. Origins and URL paths can still identify people or projects; inspect before sharing. This is not a complete anonymizer.
• This analyzes an exported HAR; it does not filter the live Chrome DevTools Network panel or contact recorded endpoints.
• The JSON exports every failed row and only the 50 slowest requests. This report does not establish a backend root cause or replay traffic.

Test pasted or imported robots.txt rules for one URL and crawler token, with an allow decision, selected group, winning rule and line number. Paste rules or choose a UTF-8 .txt file, then enter a complete URL and crawler product token.

Steps

1. Paste robots.txt or choose a UTF-8 .txt file; enter a complete URL and crawler product token.
2. Run the test and read the allow decision, selected group and winning rule with its source line.
3. Download JSON for every matching rule and ignored line number. Check the live site separately before relying on this decision.

Available options

Crawler product token

ExampleBot

Enter a crawler product token such as Googlebot, not a full browser User-Agent string.

Target URL

https://example.com/private/file

Capabilities and limits

• Tests groups, wildcards, end anchors and UTF-8 path matching locally for one HTTP(S) URL. It does not fetch robots.txt, verify its host or server status, or prove indexing.
• Paste up to 1 MiB or import one UTF-8 .txt file up to 1 MiB, with at most 5,000 lines. Unsupported or invalid lines are listed; complex matching has a calculation limit.

Audit a pasted or imported Sitemap XML file for namespace, schemaLocation pairs, URL structure, duplicates, host consistency and common optional fields. This local audit reports the first 20 issues on the page and saves the complete issue list as JSON.

Steps

1. Paste Sitemap XML or choose one UTF-8 .xml file.
2. Review document-level namespace/schemaLocation findings and entry-level URLs, dates, frequencies and priority values.
3. Download the complete JSON report, fix the source and run again. Validate against the XSD and check live pages separately.

Capabilities and limits

• Structural checks only: this does not validate the full Sitemap XSD, fetch URLs, or establish HTTP status, canonical correctness or index coverage.
• Paste up to 1 MiB or import one UTF-8 .xml file up to 10 MiB, with at most 50,000 entries. A file with no reported issues still needs schema and live-site checks.
• Checks use actual Sitemap namespaces; foreign elements with matching names do not count as URLs. A zero-entry document is not certified as a valid Sitemap.

Use a CSV headed source,target to generate exact-path location blocks with return 301 or 302. Start source paths with / and enter absolute target URLs. This output is not an Nginx map directive.

Steps

1. Enter a CSV headed source,target; source is a slash-prefixed path and target is an absolute URL.
2. Open Settings to choose 301 or 302. The site origin is used to check same-site loops.
3. Review the path, status code and target preview; download the full .conf, place its blocks inside your server block, and test with nginx -t before reload.

Available options

Redirect status

301 permanent · 302 temporary

Use 301 for a permanent move or 302 for a temporary redirect.

Current site origin

https://example.com

Enter the scheme and host, such as https://example.com, to check redirects within the same site.

Capabilities and limits

• Generates location blocks for a server context, not an Nginx map directive. A source path matches regardless of incoming query; each target URL is fixed. Review existing location conflicts and test with nginx -t before reload. This tool does not run nginx -t, test the intended site or deploy the configuration.
• Files and input stay in the browser. Paste and UTF-8 CSV files are each limited to 1 MiB; at most 1,000 rules. Outputs do not overwrite original files.
• Provide complete source paths and fixed absolute target URLs; the generator does not expand a CSV into dynamic runtime rules.

Paste one Content-Security-Policy header value without the header name. Check common source-list syntax, including malformed wildcard hosts, plus duplicate directives and broad allowances.

Steps

1. Paste the CSP header value without the header name.
2. Review invalid source expressions, including misplaced wildcards, duplicate directives, broad permissions and common missing restrictions.
3. Download the complete JSON report; verify changes with report-only mode and browser diagnostics on the actual site.

Capabilities and limits

• Local review of one policy only. Common source-list syntax is checked, but the full CSP grammar, browser support, multiple headers and report-only behavior require browser testing; findings are not a security certification.
• Files and input stay in the browser. One pasted value or UTF-8 .txt file is limited to 1 MiB. Outputs do not overwrite original files.