5 guides
Before a migration, audit the old site and run a rank check so there is a baseline. After it, crawl the new site and fix Broken internal link, Redirect chain, Page returns an error, Conflicting canonical and noindex first, then compare a fresh rank check and Search Console with the baseline.
Confirm the drop is real in the keyword's stored history, check whether the ranking URL changed, compare Search Console clicks and impressions for the same window, then audit the affected page. Change nothing until one of those names a cause.
Start with whoami for the workspace and plan, list_projects to find the domain, get_project_overview for counts and the latest audit, then get_rank_trend or get_keyword_rank_history for what moved. Read get_credit_balance before suggesting paid work. Every call reads stored rows and spends nothing.
Track the keywords whose movement would change what you do next, and save the rest. At the default depth a rank check is 40 credits per keyword per device, so 100 keywords checked weekly on both devices cost about 32,000 credits a month.
Store each rank check as an immutable snapshot — position, URL and the timestamp it was seen — rather than deriving history on read. A recomputed history can change without the SERP changing, which makes it useless as evidence.
May we set cookies to see how netweft is used? Session recordings never capture what you type. Nothing is stored until you answer, and declining still counts the visit, without a cookie. Privacy