301 redirect, canonical tag and hreflang reciprocity checker
Check in seconds whether your domain leaks link equity through 2-hop redirect chains, contradictory canonicals or broken hreflang return tags - and copy clean server rules in one click.
Short answer
Proper URL consolidation requires all three non-canonical domain variants (http://, https:// and http://www. - or vice versa) to redirect in a single permanent 301/308 hop to one target URL that declares a matching self-referencing canonical. On multilingual sites, every hreflang link from page A to page B must also be confirmed by a return hreflang link from B back to A.
What you get for free
Right away in the browser, no email needed
- Visual redirect trace across http://, https://, http://www. and https://www. with status codes and hop count
- Canonical alignment check comparing HTML <head>, HTTP Link header and final redirect destination
- Live hreflang reciprocity matrix checking HTTP 200 status and bidirectional return links + x-default
- 4 copy-paste redirect snippets tailored to your domain: Next.js, Nginx, .htaccess and Cloudflare
Free diagnostic permalink (?url=...) ready to send straight to your developer or DevOps team.
The 4 Redirect & Canonical Bugs That Quietly Drain Rankings
Frequent URL consolidation errors vs clean technical implementation
| Technical Issue | Why It Hurts SEO & AI Crawlers | Clean Fix |
|---|---|---|
| 2-Hop Chain (http -> https -> www) | Adds mobile RTT latency and weakens link equity from unformatted directory links | Collapse protocol + host rule into 1 direct 301/308 jump |
| 302 / 307 Temporary Redirect | Tells Google to keep the old URL in the index instead of consolidating signals | Replace with permanent 301 or 308 status code |
| Canonical Points to Redirecting Host | Triggers GSC "Google chose different canonical" and splits page authority | Output exact final HTTPS + host URL in <link rel="canonical"> |
| Unidirectional or 301 hreflang | Google discards the entire language cluster; wrong locale ranks in DE/UK/PL SERPs | Ensure HTTP 200 targets + full A<->B reciprocity + x-default |
Verified against Google Search Central documentation on redirects, canonicalization and localized versions.
Preparing for a CMS relaunch? Download our website migration SEO checklist and scan up to 25 subpages in our free SEO audit.
How to Build Bulletproof hreflang for PL, EN & DACH Markets
- Self-referencing tag required: Every localized URL must list itself alongside all translations in the same
hreflangcluster. - Never link to unbuilt or redirecting pages: Only emit
hreflangannotations for URLs returningHTTP 200. - Compare CMS handling: See how Next.js
next-intlcompares against WordPress translation plugins in Next.js vs WordPress for SEO and Webflow vs WordPress SEO, or review our SEO pricing (audits from €350 net).
More free tools
- Free SEO audita 1-100 score and a list of errors for up to 25 pages
- AI visibility checkwhether ChatGPT, Gemini, Perplexity, Claude and Google AI Overviews name your business
- SEO loss calculatorthe monthly profit you lose without a Google top 3 position and AI recommendations
- Website redesign mockupa new AI homepage design in 1-3 minutes, built from your content
- llms.txt generatoran llms.txt file from your sitemap and an access test for 9 AI bots and Bingbot
- Domain authority checkera 0-100 score from the Common Crawl link graph, compared with up to 3 competitors
- AI crawler & robots.txt checkertest 15 AI crawlers in robots.txt and live HTTP, spot 403 WAF blocks and check SSR parity
- Core Web Vitals comparison28-day Chrome UX Report field metrics (LCP, INP, CLS), CMS bloat X-ray and competitor showdown
- GEO citability checker6 RAG criteria across H2/H3 chunks, AI Overview snippet preview and rival comparison
- IndexNow generator & Bing testIndexNow key (.txt + GitHub Action), Bingbot & OAI-SearchBot access and lastmod entropy
- Entity graph JSON-LD validatorinteractive SVG @graph map, @id links, VAT/Tax IDs, sameAs profiles and unified JSON-LD
- Local SEO NAP & review QR toolHTML vs LocalBusiness JSON-LD NAP consistency, 5-star review calculator and vector QR code
- All free SEO tools and AI toolsthe full list, with SEO templates to download
Frequently Asked Questions: 301 Redirects, Canonicals & hreflang
Yes. Google Search Central treats both HTTP 301 (Moved Permanently) and HTTP 308 (Permanent Redirect, used natively by Next.js and Vercel) as permanent redirects that consolidate link equity and canonical signals. By contrast, HTTP 302 and 307 signal a temporary move - leaving them on HTTP or non-www variants often keeps duplicate hostnames indexed.
Every extra hop adds TLS/TCP round-trip latency on mobile networks, burns crawl budget and weakens signal consolidation when third-party directories link to a bare http://domain.com URL. A clean server rule collapses all non-canonical host and protocol combinations into a single direct jump.
Google requires every localized URL pair to confirm each other: if page A (/oferta) declares hreflang="en" pointing to page B (/en/offer), page B must include a matching hreflang="pl" link pointing back to page A, alongside self-referencing tags on both pages. Unconfirmed or 301-redirecting hreflang URLs are ignored.
The x-default annotation tells search engines which fallback version to show users whose browser language matches none of your explicit regional versions (for instance, a visitor in France when you publish PL, EN and DE). Typically it points to your international English page or primary root URL.
Sending Googlebot via 301 to https://www.example.com/ while rendering <link rel="canonical" href="https://example.com/"> creates a contradictory loop. Google Search Console flags this as "Duplicate, Google chose different canonical than user" and may split impressions across both hostnames.
Sources
- Google Search Central: redirects and Google Search (accessed November 22, 2026)
- Google Search Central: localized versions of your pages (hreflang and x-default) (accessed November 22, 2026)
Have a project in mind? Let’s price it!
Fill out our quick form and receive a tailored proposal within 24 hours.
WHAT YOU GET AFTER SENDING
- Clear quote and priority roadmap within ≤ 24 h on business days
- Quick review of indexation issues, keywords and AI visibility for your domain
- Direct reply from the SEO specialist running the work - no sales rep
- Office: ul. Grzybowska 5A, 00-132 Warszawa
- Phone: 518 815 055
- E-mail: kontakt@ai-seo-company.pl
- Opening hours: Mon-Sat 7 am-11 pm, Sunday closed
- NIP: 5253090237
- Response Time: Within 24 h on business days, usually sooner