Seite nicht gefunden

404 log

Which addresses run into nothing — and where the calls came from.

If WordPress finds nothing for a request, the log writes one row: the requested address, how often it has already been called, when first and when last, plus the referrer last seen. There stays one row per address, and the counter goes up. About the person behind the request the log records nothing. From every row you create a redirect right away — the entry is then marked as handled.

What the 404 log offers

One row per address, hits are counted up

First and last occurrence per entry

Last seen referrer, internal ones flagged

Redirect straight from a log row

Sort by frequency or time

Retention 0 to 3650 days, cleaned up daily

Here's how it works

Turn on recording and set retention

Sort the list by frequency

Create a redirect from the row

FAQ on the 404 log

What is stored about visitors?

Nothing that points to a person. The row contains the requested address and the referrer — both are details about an address. IP address, browser identifier and user name are not written along.

Does the table grow without limit?

No. The log holds at most 1000 rows; beyond that, whatever has gone unseen the longest drops out. Rows that have already produced a redirect stay untouched. On top of that you can set a retention period between 0 and 3650 days, which a daily job takes care of.

Do I also see which parameters the address was called with?

Only the path, everything after the question mark is dropped. Upper and lower case as well as a trailing slash are folded together — several spellings of the same address therefore end up in one row.

404 log

404 log

What the 404 log offers

Here's how it works

FAQ on the 404 log

More SEO features

Try SEO free for 24 hours.