Federico Rao
Technical SEO and Search Experience
Technical SEO for businesses that need organic visibility to become qualified demand: crawlable pages, clean signals, strong content, and measurable conversions.
Who this is for
Technical SEO is appropriate for businesses with a real offer and commercial website that is not being crawled, understood, selected, or converted as effectively as it should. Common contexts include service firms, clinics, agencies, founders, and content operations with indexation, rendering, architecture, performance, or measurement constraints.
Baseline before recommendations
The first pass captures what search engines and users actually receive: response status, robots directives, canonical tags, raw HTML, rendered content, sitemap entries, internal links, structured data, mobile behavior, Core Web Vitals evidence, analytics, Search Console data when available, and the current conversion path.
Crawlability and indexability
Checks cover robots rules, server and client noindex behavior, sitemap quality, canonical conflicts, redirects, soft 404s, duplicate routes, parameter handling, orphan pages, crawl depth, and whether important content depends on JavaScript execution. Technical changes are tied to a URL, file, response, or observable search signal.
Search-native rendering
Public pages should provide stable titles, descriptions, canonical URLs, robots directives, structured data, and meaningful content in initial HTML. Client rendering can enhance the experience, but critical search signals should not conflict with server output. Non-200 responses should not rely on JavaScript to become valid pages.
Money pages and intent
Commercial pages explain audience, problem, process, deliverables, limits, objections, non-fit, evidence, and a relevant next step. The page type follows search intent rather than a keyword alone. A service page, guide, comparison, case study, and tool solve different decisions and should not be generated from one interchangeable template.
Content architecture
Topic clusters connect a commercial hub to distinct supporting guides through descriptive internal links. Briefs identify primary intent, audience, angle, source needs, related pages, overlap risk, and the action expected after reading. New content is blocked when it merely paraphrases an existing page or lacks a distinct reader decision.
AI-assisted publishing controls
Automation can prepare outlines, drafts, metadata, source lists, internal-link suggestions, similarity fingerprints, and quality scores. Generated material remains draft-only until reviewed. Factual checks, source-to-claim alignment, originality, useful depth, disclosures, and cannibalization remain editorial responsibilities rather than tasks hidden behind volume.
Structured data and entities
Schema can describe people, services, organizations, articles, breadcrumbs, profiles, and collection pages when the visible content supports those entities. Markup is not used to invent reviews, ratings, frequently asked questions, credentials, or relationships. Author and editorial-policy pages give entity claims a stable, inspectable destination.
Performance and experience
Review includes loading strategy, JavaScript cost, image dimensions, layout stability, interaction responsiveness, mobile navigation, semantic elements, labels, and keyboard behavior. Lab tools provide diagnostic evidence, while field Core Web Vitals require real-user data. A score is treated as a signal to investigate rather than a guaranteed ranking lever.
Measurement and iteration
Search Console, analytics, crawl checks, PageSpeed evidence, index coverage, query-to-page fit, leads, and lead quality can be monitored after deployment. The purpose is to test whether pages are discovered, selected, read, and connected to useful actions. More impressions without qualified outcomes do not automatically represent progress.
Limits and non-fit
Technical corrections cannot guarantee rankings, traffic, citations, or revenue because competition, authority, usefulness, demand, and search systems also matter. The work is not a fit when the only objective is publishing thin pages at scale, fabricating authority, hiding commercial relationships, or pursuing tactics designed to deceive users or platforms.
Common questions
New content is preceded by review of existing pages, intent, overlap, competitor page types, sources, internal links, and measurement. Articles can be drafted automatically with quality gates, but publication still requires review. Technical foundations improve eligibility and clarity without creating a promise of ranking.
Competitor and SERP evidence
Competitor research is used to understand search intent, page type, coverage gaps, source expectations, and user objections. It is not permission to copy structure, language, proprietary data, reviews, or claims. Search results are time-sensitive and location-dependent, so observations should record the market, device or locale where relevant, and collection date.
Internal links and consolidation
Each new guide should have a relevant path from a hub and should return readers toward a useful service, related guide, project, comparison, or contact step. Existing content is preferred when it can be improved. Overlapping drafts are merged, redirected, or withheld so publication does not create several weak pages competing for the same decision.
External authority
Technical and editorial improvements operate on the site itself. Mentions, references, citations, reviews, and links from other communities require genuine participation and independent choice. Reddit, forums, directories, guest contributions, and digital public relations should not rely on fake accounts, coordinated manipulation, undisclosed promotion, or automated spam.
The next step
A useful SEO request includes the domain, target market, core services, priority locations or languages, access to Search Console and analytics where available, known migrations, publishing capacity, and lead-quality definition. That evidence supports prioritization. A generic audit without business context can identify defects but cannot decide which opportunity matters most.