HTTP status on every URL.

Every URL in Morrison now carries its HTTP status - and, for redirects, where it points. The crawler probes each page as it goes, stores the result, and shows it as a badge in the URL list and on the page detail. A redirect audit that used to mean exporting to a spreadsheet and running a separate tool is now a glance down a column.

What you see

• A status badge on every row. 200s read quietly. 301s and 302s show the redirect target next to the source. 404s and server errors stand out, so the pages that need a decision are the ones that catch your eye.
• Redirects are followed. When a URL redirects within your own domain, the destination is crawled too, so the page you actually serve is the page Morrison reads and reasons about.
• Status in the page’s history. The status is recorded with each crawl, so a page that started returning 404 after a release shows exactly when it happened.

Lists show live pages by default

The URLs overview, page search, segment previews and exports now show the pages that are actually live. Redirects, gone pages and errors stay out of the way until you ask for them - filter on status, or include everything explicitly, and they appear. Your content inventory reflects what visitors and Google can reach, and an audit prompt in Chat does not waste credits reading pages that no longer exist.

Want the opposite view? A status filter of “not 200” is a ready-made cleanup list: every redirect chain to shorten, every 404 with internal links still pointing at it, every page that quietly died.

Try it

Status is recorded on every crawl from now on, so your next scheduled crawl fills it in for the whole site. Open the URLs view, add a status column or filter, and you have the audit. Then ask Chat to prioritise the redirects that matter by the traffic the source pages still receive.

Questions, or a status you would like handled differently? Tell us at hello@morrison.app.