Support

It’s in your WordPress root as sitemap.xml. Your previous sitemap is backed up as sitemap-YYYYMMDD-HHMMSS.xml.

Yes. All public post types are included by default.

The plugin needs write access to your WordPress root to create sitemap.xml and backups.

If you use a caching plugin or CDN (e.g., Cloudflare), purge cache after generating your sitemap to see updates.

Not in v1.0. This is planned for a future release.

Currently, all URLs use defaults (e.g., weekly and 0.8). A filter hook for customization is on the roadmap.

It generates a sitemap per-site today. Network-wide generation may be added later.

As of v1.4, the UI lives on a dedicated left-menu page (Instant Sitemap) for better UX and fewer accidental clicks. Advanced users can re-add an admin-bar button with a small snippet if desired.

Yes. Developers can swap to a Tools submenu with:
add_submenu_page('tools.php','Instant Sitemap','Instant Sitemap','manage_options','instant-sitemap','instant_sitemap_render_admin_page');

No. The plugin does not send data to external services.

Yes, we recommend it. Pro includes the same Instant Sitemap generator plus JSON-LD. Removing the free plugin reduces UI clutter. Your sitemap.xml files remain intact.

The button only re-writes /sitemap.xml. Schema is added at page load based on your settings and the page context. Refresh the page and check the HTML source or use Diagnostics → Preview JSON-LD.

We try hard not to. If we detect one of these, we show a banner and start with all schema modules disabled (Coexistence Mode). You can enable specific modules if you prefer our output for those types.

No. We never modify theme files. We output JSON-LD via wp_head. If your theme already prints schema, keep our modules off or enable selectively.

Not in v1.0.0. We don’t parse or merge your theme’s JSON-LD. You choose modules; we output only those types, cleanly and predictably.

• Pages: Home → ancestor pages → current page.
• Posts: Home → (Blog page if set) → primary category chain → current post.

If a sensible trail can’t be computed, we skip breadcrumbs for that request.

v1 uses BlogPosting for single posts. Pages and custom post types are ignored in v1.

You must provide Organization Name (and optionally Logo). If left blank, we emit only WebSite to avoid guessing. This is by design.

No. The plugin does not send data to external services.

Network-activate if you want; settings are per-site.

Yes. It uses modern, standards-based markup with minimal CSS that adapts to professionally built themes (and Bootstrap 5).

Absolutely. Add multiple locations in settings (comma-separated) or use the shortcode multiple times.

Add class mega to a top-level item. Its children become columns; grandchildren are links. Configure column count in settings.

• Divider: add a child with title - or class divider.
• Header: add class dropdown-header or set the item’s Title Attribute to header.

Alignment classes like dropdown-menu-end are honored. Autoclose behavior can be set globally and overridden per item with:
dropdown-autoclose-inside, dropdown-autoclose-outside, or dropdown-autoclose-false.

Yes. CSS variables respect prefers-color-scheme. Submenus flip direction in RTL automatically.

Menus are fully keyboard-navigable (arrow keys, Tab, Esc) and use correct ARIA roles for screen readers.

Rarely. If your theme has heavy dropdown overrides, you may need a one-line CSS reset. See our docs for examples.

No. The plugin runs entirely within WordPress; no external data calls are made.