If Google cannot find your most important pages, your investment in content and link building is worthless. Every day we see sites with excellent text and spectacular design, yet they generate zero revenue because the technical side is neglected. We at Meteora Web have been working for years on projects where technical SEO was the real revenue multiplier. In this pillar guide, we cover the ten fundamental areas of advanced technical SEO, with hands‑on explanations and actionable steps.
Why Technical SEO Is the Foundation of Revenue
A beautiful site without a solid technical foundation is like a store with its shutters down. Technical SEO is not an option—it is the infrastructure that determines whether search engines can discover, understand, and index your pages. If you get crawl budget, JavaScript rendering, or structured data wrong, all your other SEO efforts lose effectiveness. We always start here: once the machine works, every content and link effort yields measurable returns.
Crawl Budget: Let Googlebot Scan the Right Pages
Crawl budget is the number of requests Googlebot can make to your site in a given time. If you have thousands of useless URLs (tracking parameters, internal search pages, print versions), Google wastes resources and may skip the pages that truly matter.
Diagnosis with Google Search Console
Go to Settings → Crawl stats in Search Console. Look at total daily requests and average response time. If the time exceeds 200 ms, you have a performance issue that reduces crawl budget.
Practical Optimization
- Block irrelevant URLs via
robots.txt(e.g.,/search?*,?sort=*). - Remove orphan pages with custom 404s and 301 redirects.
- Use
rel="nofollow"on internal links pointing to non‑strategic pages. - Improve server speed: lower response time = more pages to scan.
Immediate action: review the “Not indexed” report in Search Console and fix pages marked “Crawled – currently not indexed”—they are often slow or duplicate.
Sponsored Protocol
JavaScript SEO: Rendering and Search Engines
Google executes JavaScript, but not always like a real browser. If your site is a Single Page Application or relies heavily on client‑side JS, Google may see an empty page.
Testing Rendering
Use the “URL Inspection” tool in Search Console: the “Screenshot” tab shows what Google sees. If it’s white or incomplete, you need Server‑Side Rendering (SSR) or Static Site Generation (SSG). Frameworks like Next.js, Nuxt 3, or Laravel with Inertia support these modes.
Best Practices
- Use
<noscript>only as a fallback, not as a solution. - Avoid lazy‑loading critical above‑the‑fold images.
- Make sure links are
<a>elements with real hrefs, not handled solely via JS events.
Immediate action: install the “Google Search Preview” extension and load a page on your site with JavaScript disabled. If content disappears, you have a problem to solve.
Structured Data: Speak Google’s Language
Structured data (Schema.org, JSON‑LD) helps Google understand the meaning of your content and generate rich snippets: review stars, prices, FAQs, breadcrumbs. Sites with valid structured data can see CTRs up to 30% higher.
Implementation with JSON‑LD
Insert the script inside the <head> of relevant pages. Example for an article:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Article Title",
"author": {
"@type": "Person",
"name": "Calogero Bono"
},
"datePublished": "2026-05-20",
"image": "https://yoursite.com/image.jpg"
}
</script>Validation
Use the Schema.org Validator or Google’s “Rich Results Test”.
Sponsored Protocol
Immediate action: add BreadcrumbList and Organization structured data to every page. Done? Verify in Search Console.
Log File Analysis: Read Googlebot’s Behavior
Server logs reveal exactly which URLs Googlebot visited, how often, and with what errors. Tools like Screaming Frog Log File Analyzer or manual analysis via grep and awk provide data no online SEO tool can.
What to Look For
- URLs with 4xx or 5xx errors: Googlebot wastes time on broken pages.
- Crawl patterns: Does Googlebot visit admin or internal API pages? Block them in robots.txt.
- Frequency per page type: Are important categories scanned daily? If not, revise your internal link structure.
Quick Analysis with grep
grep "Googlebot" access.log | cut -d ' ' -f 7 | sort | uniq -c | sort -nr | head -20This shows the top 20 most crawled pages.
Immediate action: if you don’t have access to logs, ask your provider to enable them. Many hosting plans disable logs by default. We enable them for every project we manage.
Canonical Tag and URL Consolidation
Duplicate content is one of the most common causes of soft SEO penalties. The rel="canonical" tag tells Google which version of a URL should be considered the original.
Common Mistakes
- Canonical pointing to a non‑existent page (4xx): worse than not having one.
- Missing self‑referencing canonical: every page should have a canonical that points to itself.
- Multiple canonical tags: more than one can confuse the crawler.
Correct Implementation
In the <head> of every page:
<link rel="canonical" href="https://yoursite.com/correct-page" />For tracking parameters, use a canonical that excludes them.
Immediate action: install an SEO plugin (or manually edit your theme) to add self‑referencing canonical on every page. Then use Screaming Frog to find incorrect canonical chains.
Sponsored Protocol
Hreflang: SEO for Multilingual Sites
If you have multiple language versions of the same content, the hreflang attribute tells Google which version to show users of a given language or region. Getting hreflang wrong can cause penalties or show the wrong language.
Correct Implementation
In the <head> of each page:
<link rel="alternate" hreflang="it" href="https://yoursite.it/seo-tecnico" />
<link rel="alternate" hreflang="en" href="https://yoursite.com/en/technical-seo" />
<link rel="alternate" hreflang="x-default" href="https://yoursite.it/seo-tecnico" />Verification
Use the “International Targeting” report in Search Console.
Immediate action: check that all language versions reference each other. A common mistake: forgetting the x‑default tag, which serves users without a preferred language.
Advanced XML Sitemap – Priority and Frequency
XML sitemaps help Google discover new URLs, but most sitemaps are poorly managed. Priority and change frequency should be used wisely.
Parameter Optimization
<priority>: values from 0.0 to 1.0. Leave the homepage at 1.0, second‑level pages at 0.8, articles at 0.5. Do not set everything to 1.0 – Google ignores the field if all values are equal.<changefreq>: use “daily” for active blogs, “weekly” for static pages, “never” for resources that never change.
Include Only Indexable Pages
Ensure your sitemap contains only indexable URLs (no session parameters, login pages). You can generate dynamic sitemaps with Yoast SEO, Rank Math, or custom Laravel solutions.
Immediate action: download your sitemap at /sitemap.xml and check for syntax errors. Use an online validator like this one.
Core Web Vitals and Performance Optimization
Core Web Vitals (LCP, FID/INP, CLS) are usability metrics Google has considered as ranking factors since 2021. A slow or unstable site systematically loses positions.
Sponsored Protocol
The Three Key Metrics
- LCP (Largest Contentful Paint): loading time of the largest element. Target: < 2.5 seconds.
- FID / INP (First Input Delay / Interaction to Next Paint): responsiveness to first inputs. Target: < 50 ms for INP.
- CLS (Cumulative Layout Shift): visual stability. Target: < 0.1.
Concrete Actions for Improvement
- Optimized images: WebP or AVIF, exact dimensions. We reduced an e‑commerce site’s weight by 60% with automatic compression.
- CDN: distribute static assets over a content delivery network.
- Lazy loading for below‑the‑fold images.
- Reduce render‑blocking JavaScript: load scripts asynchronously.
- Responsive server: upgrade to PHP 8.2+ and enable OPcache.
Immediate action: open PageSpeed Insights with your URL and follow the suggestions. If LCP is high, your server likely responds slowly or the hero image is too large.
Internal Linking: Silo Architecture and Authority Flow
Internal links distribute authority (PageRank) among pages. A silo architecture organizes content into closed thematic areas, avoiding dilution.
Basic Principles
- Every important page should receive at least one link from a higher‑level page (e.g., homepage → category → article).
- Use descriptive anchor text, not generic “click here”.
- Avoid links to orphan pages (no incoming links).
- Maintain a maximum depth of 3 clicks from the homepage.
Analysis Tools
Screaming Frog (Spider mode) shows internal link structure and orphan pages. Use the “Diagram” view to visualize silos.
Immediate action: crawl your site with Screaming Frog, filter for “Orphan Pages”, and create links to the most important ones. Then check “Page Authority Flow” with a tool like Ahrefs or Majestic.
Mobile‑First Indexing: Check and Optimize
Since 2021, Google primarily indexes the mobile version of websites. If your desktop site is perfect but the mobile version is slow or incomplete, you risk losing visibility.
Sponsored Protocol
How to Verify
- In Search Console: check the “Mobile Usability” report.
- Use Google’s “Mobile‑Friendly Test”.
- Compare content between desktop and mobile versions: both must show the same text, images, and links.
Optimizations
- Responsive design, not a separate site (avoid m.domain).
- Font size: at least 16px for body text.
- Spacing between elements: avoid too‑close links (minimum touch target 48px).
- Reduce mobile page weight: use conditional CSS/JS to avoid loading superfluous elements.
Immediate action: open your site in Chrome DevTools with mobile emulation. Verify that all content is visible and buttons are tappable with a thumb. If something is broken, fix it now.
Summary — What to Do Now
Technical SEO is not a one‑time project but an ongoing process. Here are the actions to take this week:
- Check crawl budget in Search Console and block useless URLs.
- Test the JS rendering of your main page with JavaScript disabled.
- Add JSON‑LD structured data for BreadcrumbList and Organization.
- Analyze server logs (or enable them) to understand how Googlebot crawls your site.
- Verify canonical, hreflang, and XML sitemap with a crawling tool.
- Optimize Core Web Vitals metrics starting from what PageSpeed Insights flags as critical.
- Map your internal linking architecture and fix orphan pages.
- Test the mobile version of your site on a real device.
We at Meteora Web are here to help if these analyses seem complex. But even if you choose to do them yourself, remember: a website is measured in revenue, not compliments. Technical SEO is the first step to turning visitors into customers.
