The normal WordPress sitemap on an Nginx server is https://example.com/wp-sitemap.xml. WordPress generates that XML index and its child sitemaps; Nginx’s job is to pass the virtual URL to WordPress’s index.php instead of looking for a physical file. A static sitemap.xml is a separate design: the XML file must exist beneath Nginx’s configured document root (or an explicitly mapped alias) so Nginx can serve it directly.
Antihost offers managed WordPress hosting with free migration, one-click staging and a 14-day free trial.
This guide shows both architectures, the exact request flow, a safe Nginx configuration pattern, publication in robots.txt, optional Google Search Console submission, and tests for the failures that most often produce 404 pages or HTML where XML is expected.
As an Amazon Associate I earn from qualifying purchases.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchPC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Choose the sitemap architecture before changing Nginx
There are three common owners for a sitemap. WordPress core can generate an index dynamically, an SEO plugin can replace or extend that system, or an external process can publish static XML. Decide which component owns the canonical index first. Running two independent sitemap systems creates uncertainty about which URLs search engines should process and makes troubleshooting harder.
| Choice | Freshness | PHP dependency at request time | Operational owner | Best use |
|---|---|---|---|---|
WordPress core at /wp-sitemap.xml |
Changes with WordPress content | Yes; the normal WordPress front controller must run | WordPress core | Most standard WordPress installations |
| SEO-plugin sitemap | Depends on the plugin’s generation and settings | Usually yes | Plugin and site administrator | Sites that need plugin-specific inclusion, exclusion, or index controls |
| Static XML served by Nginx | Only as current as the generator or deployment job | No PHP request is needed | External generator and publishing pipeline | High-control environments or separately generated URL inventories |
WordPress.com documents its XML sitemap as automatic and not dependent on a third-party plugin. That supports treating a plugin as optional, not as a prerequisite for the core endpoint.
#1 Best Overall
- BLUE LIGHT BLOCKING GLASSES: Our blue light glasses for women boast UV400 protection, blocking harmful blue rays from computer screens. With these bluelight glasses women, you can enjoy gaming, reading, or watching TV with no worries of eye strain.
- EYE RELIEF: Our blue light glasses are engineered to reduce blurry vision or strain caused by prolonged screen time. These womens blue light glasses aid in better sleep by preventing blue light from disrupting your natural sleep cycle, helping you fall asleep faster and enjoy a more restful night's sleep, making them the perfect christmas present.
- COMFORTABLE: Crafted from durable material, our trendy blue light glasses for woman or blue light glasses men ensure long-lasting comfort. The high-transmittance lenses accessories, gamer gifts for men, help keep your eyes relaxed. Perfect stocking stuffers, gifts for gamers men, christmas gifts for men, halloween costumes.
- LIGHTWEIGHT: These clear blue light glasses feature a lightweight frame, meaning they’ll stay comfy for long-term wear. Perfect as blue blockers glasses for women or mens blue light glasses, these non-prescription fake glasses for men can be worn throughout the day. The blue light blocking glasses women feature polycarbonate HD lenses, which are anti-reflective and restore true color.
- WORRY-FREE PURCHASE: If you experience any issues, our support team is ready to assist you quickly. These are the perfect costume glasses for cosplay dressing up.
What WordPress and Nginx each do
WordPress creates a virtual endpoint
WordPress core’s WP_Sitemaps system registers a rewrite route matching wp-sitemap.xml and routes for its sitemap providers. It renders the index and child XML documents when WordPress handles the request. The index normally lists additional sitemap URLs rather than containing every page URL in one document.
Nginx must use the front controller
Nginx does not find a file named wp-sitemap.xml in the web root because the core sitemap is generated. A server block that only serves existing files therefore returns 404. The request must fall through to /index.php, where WordPress’s rewrite and sitemap code can answer it. This is the same front-controller pattern used for ordinary WordPress permalinks.
A static file follows a different path
For a static sitemap, Nginx maps the request URI to an actual XML file under root or an alias. PHP is not involved. Do not configure a physical /sitemap.xml and then expect it to answer WordPress’s different /wp-sitemap.xml route; each URL needs its own owner and configuration.
Prerequisites and decisions
- Administrative access to the Nginx server block serving the public hostname.
- A working WordPress installation with a reachable PHP-FPM upstream or socket.
- The correct filesystem path for the site’s document root.
- Knowledge of whether a plugin or external generator already owns a sitemap.
- A public HTTPS hostname that can be tested while logged out.
Managed hosting users should check their provider’s supported configuration process before editing Nginx. The exact PHP-FPM socket, upstream name, include file, TLS settings, and reload command vary by distribution and hosting layout. Copying another server’s socket path can break every PHP request.
Rank #2
- WINDEX GAMING WIPES: effortlessly clean all your gaming gear and gaming electronics in one easy step with our new Windex Gaming Wipes
- AMMONIA FREE: our ammonia-free formula is safe to use on all of your favorite gaming equipment like consoles, headsets, controllers, screens, keyboards, and more
- PRE-MOISTENED WIPES: each wipe instantly removes dust, dirt, and stubborn smudges and fingerprints leaving a streak-free shine
- ANTI-STATIC: great for cleaning and wiping down your gaming gear and electronics leaving behind no visible residue
- COMPACT RESEALABLE PACKAGE: store your pack of Windex Gaming Wipes anywhere in your home for whenever a quick and easy wipedown is needed
Set up the native WordPress sitemap
1. Confirm the endpoint before editing configuration
Open https://example.com/wp-sitemap.xml in a private browser window or request it while logged out. If it already returns an XML sitemap index, the application may be correctly configured and no Nginx change is necessary. Inspect the index for child sitemap URLs and test at least one of those URLs publicly.
If the endpoint returns 404, continue with the server-block checks below. If a plugin returns a different canonical sitemap, identify that URL first and choose whether the plugin or WordPress core should remain the sole owner.
Free tools Windows power users keep installed
One-click scans. No signup required.
2. Keep the document root and PHP handler together
Use the normal WordPress Nginx front-controller pattern in the relevant server {} block. Adapt the hostname, root path, FastCGI include, and PHP-FPM upstream to the host; the example is a pattern, not a universal socket configuration.
server {
server_name example.com;
root /var/www/example.com;
index index.php;
location / {
try_files $uri $uri/ /index.php?$args;
}
location ~ .php$ {
include fastcgi.conf;
fastcgi_intercept_errors on;
fastcgi_pass php;
}
}The try_files directive checks real files and directories first. When neither exists, it internally redirects the request to /index.php while preserving the query string. That fallback is what allows /wp-sitemap.xml, post permalinks, and other WordPress routes to reach PHP. The PHP location then sends the script to the configured PHP-FPM upstream.
Rank #3
- Ergonomic & Adjustable Design: Fight "text neck" and improve your posture. Designed for comfort, it offers an adjustable height (7.1in-8.5in) (1.4in adjustable range) and angle (5°-85°) Please note: cell phone stand is only 9 inches tall—the length of a standard pencil
- Without blocking subtitles Perfect for office desk Tiktok Face Time Zoom video—this is the ultimate kitchen desk essential for phones! Perfect viewing experience while reducing neck back strain, A must-have for gamers streamers desk, and anyone who values both style and support!
- Sleek & Stable Design fits Otterbox Case: Say goodbye to bent cables, tangles, and tip-overs! LISEN’s stylish adjustable desk phone holder features a built-in charging hole and smart cable management, keeping your phone secure and your workspace clutter-free cool gadgets for men
- ANTI-SLIP DESIGN free hands: The under 10.00 items easy gadgets back and the bottom of this kitchen essentials for women are fully covered by anti-skid silicone, which LISEN stand up desk decor can provide maximum protection device from any scratches and slides
- Your Perfect Viewing Companion:If your product arrives damaged or breaks within 365 days, reach out to LISEN for a quick and hassle-free solution. Struggling with assembly, like tightening the screw? We’ve got your back! Your experience matters to us. (Product including: phone Holder stand*1, screw*1, hexagon screwdriver*1, specification*1)
3. Check the active configuration safely
- Save the change in the server block that actually serves the sitemap hostname. A different block may be selected because of the hostname, address, port, or TLS listener.
- Run the distribution’s Nginx configuration test, commonly
nginx -t. Do not reload if the test reports a syntax or include error. - Reload Nginx using the host’s service-management command after the test succeeds. The exact command depends on the operating system and installation method.
- Request
/wp-sitemap.xmlagain from the public HTTPS hostname, not from an internal address or an authenticated admin session.
4. Validate the generated index and child documents
A successful result should have an HTTP 200 status, an XML response, and child sitemap URLs that resolve on the same public installation. Follow every listed child URL far enough to confirm it is reachable without a login, maintenance page, or host mismatch. Verify that HTTPS, the canonical hostname, and any subdirectory or multisite base path are consistent across the index and its children.
Publish the sitemap in robots.txt
Expose one fully qualified sitemap URL with a line in robots.txt:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Sitemap: https://example.com/wp-sitemap.xmlFor a public WordPress site, WordPress can append its sitemap index to the generated robots.txt response. A physical robots.txt file, an Nginx location, a maintenance layer, or another application can mask that generated response. If you maintain a physical file or override the response, retain the canonical Sitemap: line yourself. WordPress adds the generated line only when the site is public.
Use the exact index owned by your chosen system. If an external generator publishes sitemap-index.xml, reference that filename instead of wp-sitemap.xml; do not list competing indexes merely because both happen to exist.
Rank #4
- Easy Installation: Our gaming lights have been designed to enhance your entertainment experience. Simply position the led light bar next to your TV or game console to create a game room environment with ease. They come with USB power and a 60 inch cord for direct mounting and mobility
- Audio Syncing & Extensive Mode: The built-in high-sensitivity music sensor allows you to sync the TV led lights to your favorite music. Lights react and move to the beat of music, film and game audio, creating an incredible immersive sound and light experience – and all without the need for an additional hub. You can choose from 64+ patterns, including strobe, illusion, jump, energy, gradient, running, chasing, fluttering mode etc. Each mode can be applied to different scenes
- 64+ Chasing IC+RGB & W Effect: The independent control design of IC+RGB and white all-in-one multifunctional rgbw led bar lights monitor backlight allows you to easily switch the led lights for desk between IC+RGB and white to enjoy a variety of lighting effects, you can choose white lighting mode with high brightness for better illumination when working, etc. Choose IC+RGB lighting mode when you need to create an entertaining atmosphere for the light show, 16 million colours of Color changing rgb light bar let you dance to the beat and create a dynamic party atmosphere
- Dynamic and Dimmable Lights: 1%-full brightness free brightness adjustment gives you the flexibility to adjust dimmable led light bar for room decorations or a variety of occasions
- USB Powered: USB light bars for room can be powered by powernank, usb charger, TV, Monitor, laptop PC mainframe, making behind TV led lighting bar easy to install in any location.TV led lights are powered by the TV usb interface / PC mainframe, can be turned on/off synchronously with TV / PC
Submit the index to Google Search Console (optional)
Search engines can discover a sitemap from the robots.txt declaration. Google also accepts sitemap indexes in Search Console. Submit the same canonical URL you published publicly when you want processing status and error reporting. Submission does not repair an inaccessible URL: the index and every child sitemap still need to return valid XML over the public hostname.
- Open the property that matches the sitemap’s protocol and hostname.
- Use the Sitemaps section and enter the canonical index path, such as
wp-sitemap.xml, when the property already supplies the site prefix. - Submit it and review the reported status and discovered errors.
- Investigate HTTP, XML, redirect, or permission failures on the server before resubmitting.
Serve a static XML sitemap through Nginx
Choose this architecture when another generator owns the XML and a deployment job publishes the finished file. Place the file beneath the configured Nginx root, or map a controlled directory with alias. The request then bypasses PHP and is served as a normal static asset.
Exact-file location
location = /sitemap.xml {
try_files $uri =404;
add_header Cache-Control "public, max-age=3600";
}The exact-match location prevents an unrelated route from answering the sitemap URL. try_files $uri =404; makes a missing publication fail clearly instead of falling through to an application page. The one-hour cache policy is an operational example; choose a lifetime that matches how often your publishing job replaces the file. If the file is named sitemap-index.xml, request and publish that exact name, and use it in robots.txt and Search Console.
Root, alias, and permissions
With root /var/www/example.com;, a request for /sitemap.xml maps to /var/www/example.com/sitemap.xml. An alias can map the location to a different directory, but its trailing-slash behavior and file permissions must be checked carefully. The Nginx worker needs read access to the generated file and every parent directory. A deployment that writes a temporary file and renames it into place can avoid exposing a partially written XML document; the generator, not Nginx, is responsible for keeping the content current.
Best Value
- Compatible with Wide Screens - To ensure compatibility with the dual monitor mount, your each monitor must meet three conditions at the same time: First, computer screens size range: 13 to 32 inches. Second, screen weight range: 4.4 to 19.8 lbs. Third, the back of the monitor screen must have VESA mounting holes with a pitch of 75x75mm or 100x100mm.
- Regarding the compatibility with desks - Your desk must meet three conditions at the same time: First, desk material: Only wooden desks are recommended, plastic or glass desks cannot be used. Second, desk thickness range: 0.59" - 3.54". Third, the bottom of the desk should not have any cross beams or panels, as this will interfere with installation. We recommend carefully checking that your desk and monitors meets all above conditions before purchasing.
- Dual C-Clamp Hold - Worried your dual monitors might wobble or slip? Our upgraded base uses a larger platform plus a dual C-clamp structure to lock the dual monitor arm firmly to your desk. Each arm safely keeps your screens steady while you type, click and game—no shaking, no sliding, just a clean and secure setup you can trust every day. It also provides Grommet Mounting installation choice, both options ensure stable and secure fixation for your 0.59" - 3.54" desk.
- Full-Motion Adjustment For Comfortable View - Pull the screen closer when you’re deep in a spreadsheet, push it back to watch videos, or rotate to portrait for coding — moving everything smoothly with just one hand. The monitor stand offers +85°/-50° tilt, ±90° swivel and 360° rotation. Raise your monitor up to 15.75″ to support a healthy sitting posture. Whether you’re working from home, gaming through the night, or switching between video calls and documents, getting the screens to your natural line of sight helps relieve neck, shoulder and back strain so you can stay focused longer with less fatigue.
- Keep Your Desk Organized: By lifting both screens off the desktop, this dual monitor stand opens up valuable space for your keyboard, notebook, docking station or a simple, clutter-free work area. Built-in cable management guides wires along the arms, keeping cords out of sight and out of the way. Enjoy a tidy, modern workstation that looks as good as it feels to use.
Test the public response before declaring success
Test from outside the server and record the final URL, status, headers, and body. These checks catch routing mistakes that a browser’s rendered view can hide.
Check status, redirects, and content type
curl -I https://example.com/wp-sitemap.xml
curl -sS -D - -o /dev/null https://example.com/wp-sitemap.xml
curl -sS https://example.com/wp-sitemap.xml- Expect a successful status, normally 200, for the canonical URL.
- Confirm that any redirect ends at the intended HTTPS hostname and does not require authentication.
- Inspect
Content-Typefor an XML media type rather thantext/html. - Read the body and confirm it begins as a sitemap index or sitemap document, not a login, maintenance, or generic error page.
Check every child sitemap
Copy each child URL from the index and repeat the status, redirect, content-type, and body checks. A valid index with broken child URLs is not a complete sitemap installation. Pay particular attention to subdirectory WordPress sites, multisite paths, and mixed HTTP/HTTPS links.
Check compression and caching behavior
Request the endpoint with and without an Accept-Encoding header to see whether Nginx or an upstream adds compression. Compression is optional, but it must not change the response into HTML or truncate the XML. Inspect Cache-Control, ETag, and Last-Modified headers if a proxy or CDN is present. A cached response should still be the correct sitemap owner and should refresh according to the publishing schedule.
Check robots.txt
curl -sS https://example.com/robots.txtConfirm that the response is the intended robots policy and contains one correct, fully qualified Sitemap: line. If the line is missing, determine whether a physical file or Nginx location is masking WordPress’s generated response.
Troubleshoot common failures
| Symptom | Likely cause | Fix |
|---|---|---|
404 on /wp-sitemap.xml |
The request never reaches WordPress, or the wrong server block is active. | Verify the active hostname and TLS server block, retain try_files $uri $uri/ /index.php?$args;, confirm the document root, and ensure PHP-FPM is reachable. |
| Nginx downloads or exposes PHP | The PHP location or FastCGI pass-through is missing or incorrect. | Use the distribution’s tested FastCGI include, correct the fastcgi_pass upstream or socket, and verify the script filename parameters supplied by that include. |
| HTTP 200 but the body is HTML | A login page, maintenance page, catch-all route, or redirect target answered the request. | Inspect the final URL and Content-Type, test while logged out, and trace which location or upstream generated the HTML. |
robots.txt lacks the sitemap line |
The site is not considered public, or a physical file/Nginx location masks the generated response. | Make the public response intentional and add the fully qualified canonical line to the file or override that is actually served. |
| Child sitemap URLs fail | Host, HTTPS, subdirectory, multisite, or authentication settings differ from the index. | Correct the canonical base URL and test every child URL without credentials. |
| Two sitemap indexes are published | WordPress core, a plugin, and/or an external generator are all claiming ownership. | Select one owner, remove or disable competing routes, and publish and submit only its canonical index. |
Static /sitemap.xml returns an application page |
No exact static location exists, or the file is absent beneath root/alias. |
Place the generated file at the mapped filesystem path, add the exact-match location, and use try_files $uri =404; to expose missing publications. |
Operational ownership and maintenance
Dynamic WordPress sitemaps require the normal WordPress front controller, PHP-FPM, and the site’s application availability. Their advantage is automatic updates as content changes. Static sitemaps remove PHP from the request path, but the external generator and deployment job become responsible for freshness, atomic publication, permissions, and rollback. Document that ownership so a future administrator does not enable a second sitemap plugin or overwrite the file unexpectedly.
After WordPress, Nginx, PHP, a plugin, or the generator changes, repeat the public checks. A configuration test proves syntax, not routing; a 200 response proves reachability, not that the body is XML; and a valid index does not prove its children work. Treat status, final URL, media type, body, child URLs, robots declaration, and cache behavior as one acceptance checklist.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesRecommended decision
For an ordinary WordPress installation, keep WordPress core’s /wp-sitemap.xml and use the standard Nginx front-controller fallback. Choose a plugin-owned sitemap only when its controls are genuinely required, and choose a static file when an external publishing pipeline is the deliberate source of truth. In every case, advertise one fully qualified index URL, test it anonymously from the public hostname, and submit that same URL only when you want Search Console reporting.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
