How your sitemap and search-engine submission work
This page explains how MapleGather keeps your sitemap current and public on its own. You never run a sitemap generator or upload a file by hand. It also explains what that does, and what it doesn’t do.
The short version
Section titled “The short version”Your site’s sitemap is built fresh every time a search engine asks for it, so it reflects your latest publish straight away. It stays published at your site’s sitemap.xml address. There’s no generator to run, nothing to regenerate, and no file to upload. A current public sitemap is how search engines find and re-read your content.
What MapleGather does not do today is notify Google or Bing. That step is switched off, so nothing is sent to either of them. The SEO status page has a “Recent pings” list and Google and Bing tiles. They show what MapleGather logged at your last publish. They are not a reply from the search engine. If search traffic matters to your group, submit your sitemap address once in Google Search Console. That is the step MapleGather isn’t doing for you.
How it works
Section titled “How it works”A sitemap is a simple list of your public pages that search engines read to discover your content and notice what’s new. In some tools you have to build and maintain that list yourself. In MapleGather, you don’t.
Here’s what happens on its own:
- Your sitemap is always current, and there is nothing to regenerate. MapleGather builds the sitemap from your live pages at the moment a search engine asks for it. So the instant you publish or update a page or a blog post, the sitemap already matches what’s actually live — there is no rebuild step to run, wait for, or miss.
- Search engines find the change by reading that sitemap. A current, public sitemap is the mechanism — crawlers re-read it and pick up what’s new. This is the part that genuinely happens on its own.
- The direct notification step is recorded, but not switched on. MapleGather has a step that would ping Google and Bing right after you publish, and it writes an entry to the “Recent pings” list on the SEO status page each time it runs. That step does not currently send anything to either search engine. Read those entries as MapleGather’s own log of the step, not as the “submit to search engines” step other tools make you do by hand — that one is still worth doing once yourself, in Google Search Console.
- Your sitemap and robots file stay public and current. They’re served at your site’s
sitemap.xmlandrobots.txtaddresses. Add/sitemap.xmlor/robots.txtto your site address any time to see exactly what search engines see. - Some pages are left out for you. Drafts stay out of the sitemap until you publish them, and a page you have set to members-only stays out as well — MapleGather never points a search engine at content the public cannot read. There is no per-page “leave this one out” switch in the page editor today; if you need a published, public page kept out of search results, tell us.
Why it works this way
Section titled “Why it works this way”Doing this by hand is easy to get wrong. The old way went something like: run a generator, download a file, upload it to your site, then open each search engine’s webmaster tool and paste in your address — and repeat parts of that every time you change a page. It’s fiddly, it needs a bit of technical know-how, and it’s easy to forget. When you forget, your newest content can stay invisible to search for weeks.
MapleGather takes the repeating part of that off your plate — the generating, the uploading, and the re-doing of it after every single edit. A volunteer running the site on a Saturday morning doesn’t have to learn any of it, and a full-time communications admin doesn’t have to remember a checklist after every change.
There is one step it doesn’t do for you. That’s the first-time one: telling each search engine where your sitemap lives. It takes a few minutes in Google Search Console, and you only do it once.
Edge cases & boundaries
Section titled “Edge cases & boundaries”- A ping entry can record a failure, and it costs you very little. That shows as “Not delivered” in the Recent pings list on the SEO status page. It never blocks your page from publishing, and your sitemap is still current and still public — which is the part that actually matters for discovery. It’s worth a look rather than a shrug if it keeps happening across several publishes, but it is not a reason to hold back a publish.
- A ping entry isn’t evidence of anything at the search engine — in either direction. A “Pinged” entry means MapleGather recorded its notification step as complete; it does not mean Google or Bing received, read or acted on anything, and while that step is switched off it does not mean anything was sent. Whether and when a search engine lists your page is up to them, and the only place to see the real answer is Google Search Console — select Open Google Search Console on the Google tile of the SEO status page. It opens in a new tab.
- Drafts aren’t included. Only published pages and posts appear in your sitemap. A page stays out until you publish it.
- Members-only pages are handled separately. Gated pages follow your robots policy and content gating rather than being advertised to anonymous search crawlers. You set the members-only crawling rule in your SEO settings.
- There’s no manual generator to run. If you’re used to one from another tool, there isn’t one here — by design — and there’s nothing to upload.