Keep Googlebot access rules current when IP ranges change
Verify crawler requests, update the correct Google IP range list, and check that your CDN or firewall actually applied the change.
Read article →Field notes
Step-by-step checks, code examples, and explanations for technical SEO and tracking problems.
Verify crawler requests, update the correct Google IP range list, and check that your CDN or firewall actually applied the change.
Read article →Identify Googlebot, image crawlers, AdsBot, and inspection requests separately. Keep the original log data and verify requests before allowlisting them.
Read article →Give an author, publisher, or article one consistent identifier so your JSON-LD blocks describe the same entities across pages.
Read article →Use real publication, update, offer, and event dates in your structured data. Find expired values and stop templates from inventing a new date on every request.
Read article →If important images are missing from search, check their public URLs, image markup, CDN access, and format handling before rewriting alt text.
Read article →Compare initial HTML with rendered output to find blocked resources, failed API requests, and content that depends on clicks or scrolling.
Read article →Use verified logs to compare product pages, duplicates, redirects, and errors before changing crawl rules or sitemap generation.
Read article →Review empty archives, duplicate filters, and other generated URLs. Keep useful landing pages and choose the right control for the rest.
Read article →What llms.txt can do, what Google requires for AI search, and examples for publishing a maintained directory of your public pages.
Read article →Make deeper products and articles reachable through ordinary links. Check page URLs, canonical tags, infinite scroll, and pages beyond the end.
Read article →