Azrested introduced this Site Updates section as a permanent home for indexer status reports, application changes, maintenance notes, and publishing news. The same release tightened how public routes communicate with search engines so discovery is focused on useful, stable pages.
A dedicated public change log
Operational and application changes previously had no single public destination. The new archive collects dated updates in chronological order and assigns each entry to one of three clear categories: Site Update, Indexer Status, or Application News.
The homepage surfaces the three most recent entries, while the full archive preserves the broader timeline. Each substantive update has its own permanent URL, publication date, category, reading time, and links to neighboring updates.
Search-engine indexing controls
Not every URL produced by an application belongs in a search index. The routing policy now treats each public URL according to its purpose:
- stable public pages and substantive published updates can be indexable;
- internal search results are marked noindex;
- filtered browse variants are kept out of the index and point back to a clean canonical page;
- empty archives do not advertise themselves as useful search destinations; and
- thin, preview, draft, and error states remain excluded.
When query parameters create alternate views of the same destination, the canonical signal identifies the clean public URL search engines should treat as primary.
Pagination behavior
Paginated archives need to remain navigable without producing conflicting canonical signals. Valid archive pages retain sensible navigation, while parameterized or low-value variants are prevented from competing with the main destination. Requests beyond the available page range are handled as errors rather than presented as empty indexable pages.
A cleaner XML sitemap
The sitemap now focuses on approved public pages, valid county destinations, eligible arrest records, the populated updates hub, and substantive update articles. Internal searches, filters, empty sections, drafts, previews, and retired sitemap routes are excluded or redirected as appropriate.
This approach keeps sitemap membership aligned with the same publication rules used for robots and canonical output. A URL should not appear in the sitemap merely because WordPress can generate it.
Interface changes included
The release also corrects homepage county-card text flow and makes the primary Browse a County, Search One Record, and Review a Page titles directly clickable. The new update articles use an expanded editorial layout with structured sections, release details, verification guidance, and clearer previous and next navigation.
How the controls are checked
Automated tests cover robots directives, canonical output, update archive state, sitemap membership, and representative public routes. Local smoke checks confirm that the homepage, county directory, REST entry point, and sitemap respond successfully. These checks reduce regression risk as future application and indexer changes are published.
What comes next
This section will continue to document changes that materially affect the public site, its data-processing status, or how visitors use the application. Current official facts still belong with the responsible Arizona jail, court, clerk, or agency; Site Updates describes Azrested itself.