Technical health
Understand crawling, indexing, schema, page speed, redirects, Core Web Vitals, site structure, mobile performance, and redesign risk.
Technical foundations
Make your site easier to crawl, understand, and use.
Search visibility begins with a reliable website. Understand indexing, page performance, site structure, and how to protect organic traffic through changes.
Question library
Explore direct answers about crawling, indexing, Core Web Vitals, page speed, mobile-first indexing, redirects, schema, and redesign risk. Each question links to its original in-depth Allen Ink answer page.
Technical SEO is the work that makes a site crawlable, indexable, fast, secure, understandable, and structurally sound for search engines. It covers areas such as redirects, canonicals, sitemaps, rendering, structured data, performance, and architecture.
Read full answer →Structure determines how easily users and crawlers can find important pages and understand their relationships. A logical hierarchy, descriptive URLs, navigation, breadcrumbs, and internal links help distribute context and authority.
Read full answer →Possible causes include noindex directives, robots blocks, duplicate or thin pages, canonical tags pointing elsewhere, weak internal links, crawl errors, server issues, or Google deciding the pages do not provide enough unique value.
Read full answer →A sitemap is a machine-readable list of important URLs that can help search engines discover and monitor pages. Most business sites should maintain an accurate XML sitemap, especially when content changes regularly.
Read full answer →robots.txt tells compliant crawlers which areas they may or may not crawl. It is not a secure way to hide sensitive information and should be configured carefully because blocking important assets or pages can cause SEO problems.
Read full answer →A canonical URL tells search engines which version of similar or duplicate pages should be treated as the preferred version. Canonicals are hints, so internal links, redirects, and sitemap URLs should reinforce the same choice.
Read full answer →Core Web Vitals are Google's user-experience metrics focused on loading performance, visual stability, and responsiveness. They are useful performance benchmarks and one part of Google's broader page-experience systems.
Read full answer →Speed can affect user experience and is part of page-experience evaluation, but it is not a magic ranking lever. Improving speed is most valuable when it also improves crawling efficiency, engagement, and conversions.
Read full answer →Aim for pages that feel fast on real mobile connections, with strong Core Web Vitals and minimal blocking scripts or oversized media. The exact acceptable load time varies, but users should see useful content almost immediately.
Read full answer →Yes. Google primarily evaluates the mobile version of content, and poor mobile usability can hurt engagement and crawling. Responsive layout, readable content, fast loading, and functional navigation are essential.
Read full answer →Mobile-first indexing means Google generally uses the mobile version of a page for indexing and ranking. Important text, links, structured data, and metadata should not disappear on mobile.
Read full answer →Yes. Heavy client-side rendering, blocked scripts, delayed content, and rendering errors can make crawling and indexing harder. Modern JavaScript sites can rank well when server delivery, routing, rendering, and crawlability are handled correctly.
Read full answer →Schema markup is structured data that describes entities and content in a machine-readable format. It can help search engines understand organizations, local businesses, products, articles, breadcrumbs, events, and other page types.
Read full answer →Common useful types include Organization or LocalBusiness, Service, BreadcrumbList, Article, Product when applicable, and other schema that accurately reflects visible content. Do not add markup for information users cannot see.
Read full answer →Broken internal links waste crawl paths and frustrate users, while broken inbound links can lose referral and authority value. Fix important 404s, update internal links, and redirect old URLs when a relevant replacement exists.
Read full answer →A 301 redirect permanently sends an old URL to a new one. Use it when pages move, URLs change, content is consolidated, or old high-value pages are replaced by a relevant new destination.
Read full answer →A redesign can improve or damage SEO depending on whether URLs, content, internal linking, metadata, redirects, structured data, performance, and crawlability are preserved. SEO migration planning should happen before launch.
Read full answer →Inventory important URLs and rankings, preserve strong content, map redirects, keep metadata and internal links intentional, test staging crawlability, verify analytics and Search Console, and monitor indexing closely after launch.
Read full answer →Usually, important services deserve dedicated pages when customers search for them separately and each page can provide meaningful unique information. Avoid splitting closely related services into thin pages solely to create more URLs.
Read full answer →Internal links help users discover related information and help search engines understand page relationships and relative importance. Use descriptive anchor text and link naturally from strong relevant pages to priority pages.
Read full answer →URLs should be short, readable, stable, descriptive, and logically organized. Avoid unnecessary parameters, dates, IDs, keyword repetition, and frequent URL changes.
Read full answer →Yes. Titles remain important for relevance and search-result presentation, while meta descriptions can influence how listings are described and clicked. They should be accurate, concise, and written for the actual page intent.
Read full answer →Duplicate problems can come from URL parameters, print versions, HTTP/HTTPS variations, trailing-slash variants, copied location pages, syndicated text, or multiple pages targeting the same intent. Canonicals, redirects, and content consolidation can help.
Read full answer →Poor hosting can cause downtime, slow response times, security incidents, crawl failures, and unstable performance. Hosting is not a direct ranking shortcut, but infrastructure quality affects several things search engines and users depend on.
Read full answer →At least periodically and after major site changes. Competitive or frequently updated sites benefit from ongoing monitoring, while smaller stable sites should still review indexing, errors, performance, structured data, and redirects several times a year.
Read full answer →Need help applying it?
Connect better site structure, technical SEO, mobile performance, and careful URL planning to an actionable search visibility strategy.
