Site index

Every content page on Temp Postal, grouped by cluster. This directory exists so no page sits more than two clicks from the homepage — for readers and for crawlers alike.

More for developers

More for business and enterprise teams

More guides

More use cases

More case studies

More glossary entries

Quick answer

What is on the Temp Postal site index?

The site index is a complete, human-readable map of every public page on Temp Postal, grouped by purpose: the mail tool itself, product and pricing pages, developer documentation, guides, glossary entries, regional pages and the full article archive. It is the fastest way to find a page when search has not surfaced it.

Every public URL in one place, grouped rather than alphabetised.
Kept in step with the machine-readable sitemap, so nothing is listed that does not exist.
Useful for readers, crawlers and AI systems building a picture of the site.
Pages that redirect or require an account are deliberately excluded.

How the index is organised

Groups follow intent rather than folder structure. Someone looking for the tool wants the mail surfaces together. Someone integrating wants the developer pages together. Someone researching wants the glossary and the article archive next to each other. Sorting purely by URL would scatter all three.

Within a group, pages are listed in the order that makes sense for a reader arriving cold: the overview first, then the specifics. Where a page belongs in two groups it is listed in the one where most people look for it, not in both.

How it stays accurate

The index is generated from the same source as the XML sitemap, so a page cannot appear here and be missing there. Paths that redirect elsewhere are filtered out, as are account, billing and admin screens that require a session.

That filtering matters for search engines as much as for readers. A hub page full of links to redirects wastes crawl budget and signals neglect, so the guard that checks for those links runs with the test suite.

Machine-readable equivalents

Crawlers should use the XML sitemap. AI systems that want a compact inventory with descriptions can use the plain text corpus files we publish, which list every indexable page with its title, description and a short answer excerpt.

All of these are generated from the same page list, so there is no drift between what a person sees here and what a machine reads elsewhere.

Frequently asked questions

How is this different from the sitemap?

The XML sitemap is for crawlers and carries change dates. This page is for people, grouped by what you are trying to do rather than by path.

Why are some pages missing?

Pages that redirect somewhere else, and any screen that needs an account, are left out on purpose. Listing them would send readers and crawlers to dead ends.

How often is it updated?

It regenerates with the site, so a new page appears here as soon as it is published.

Can I link to this page?

Yes. It is a stable URL and a reasonable place to point someone who wants the whole picture.

Is there a machine-readable version?

Yes, three: the XML sitemap, a compact text inventory and a fuller corpus file aimed at AI crawlers.