301→302301→302
A temporary redirect where a permanent one belongs.
Found by Redirect checker →
redirect loopredirect loop
The URL redirects back to itself and never settles.
Found by Redirect checker →
Data sources

Yandex Webmaster integration

Read Yandex Webmaster query data per URL and keep it next to the crawl.

Yandex Webmaster integration

Queries per URL

webmaster-url-queries returns search queries for a page.

How it works

Three steps, one saved scan

  1. Point it at a verified host

    The command needs a Yandex Webmaster host ID for a site you have verified, plus the OAuth token configured locally. Without the host ID it does not run.

  2. Pull queries for a URL

    Ask for one exact page with --url, or a group with --url-contains. Caps are explicit: --max-urls and --max-queries-per-url, with optional --start-date and --end-date.

  3. Join the rows to your crawl

    Keep URL and query rows separate. The evidence-join step attaches URL-keyed rows to a crawl and lists orphan candidates for review without changing the crawl.

How to run it

One command

bash
seohead webmaster-url-queries --url https://example.com/

Install first: installation guide. Every command also runs as an MCP tool for AI agents.

Learn more

From the blog and glossary

FAQ

Questions

Yandex Webmaster integration
Yes. The command takes a verified host ID (--host-id) and an OAuth token set up on your machine. SpiderHead does not create accounts or sign in for you.
No. It is a read-only request. It returns query statistics for the URLs you name and writes nothing back to Yandex or to the site.
No. Each URL keeps its own query rows. CTR and average position are not summed across pages, and the response states the caps it applied.
Nothing beyond the Yandex Webmaster API quota. The toolkit lists the provider as free within that quota.
Yes, with sources-sync. It stores daily Webmaster evidence in a local SQLite history, so you can build up data over time.

Check your redirects locally