Technical SEO services encompass audits and corrections to a website’s infrastructure so Google can find, crawl, interpret, and index it without problems. However strong the content may be, a single line in robots.txt, an incorrect canonical tag, or a forgotten noindex rule can prevent a page from entering search results at all. Technical SEO analysis identifies these issues through Search Console data, site crawling, and server responses; corrections are made at the source of the problem.
Below, the audit checklist, indexing statuses, solutions to common problems, and topics specific to large websites are explained using Google Search Central and web.dev documentation. Audits and corrections are performed remotely; businesses in Istanbul can meet in person in Maltepe if preferred.
Let’s examine your website’s technical condition together
An initial review is performed when the website address and observed symptom (unindexed pages, falling impressions, slowness) are sent through WhatsApp. If Search Console access is available, the assessment starts directly with that data.
What are technical SEO services, and what do they cover?
Technical SEO services are infrastructure work that removes obstacles from every stage of Google’s discovery, crawling, rendering, and indexing of website pages. Google Search Central explains that pages containing JavaScript are processed in three stages: crawling, rendering, and indexing; the technical audit tries to identify at which stage losses occur. The scope consists of the following areas:
- Crawl access: robots.txt rules, server response codes, server errors, and pages Googlebot cannot reach
- Indexing checks: noindex rules, canonical tags, duplicate pages, and reasons for statuses in Search Console
- Site architecture: Internal links, redirects, URL structure, and the sitemap
- Rendering: Whether Googlebot can see content and links that depend on JavaScript
- Page experience: Core Web Vitals metrics, mobile appearance, and HTTPS
- Structured data and language versions: Markup errors and hreflang relationships
Keyword selection, content planning, and link work fall within the SEO search engine optimization service; technical work prepares the foundation on which these efforts can produce results.
Technical SEO analysis: website audit checklist
Technical SEO analysis is based on crawling the entire website with a crawling tool and comparing findings with Search Console data. Not every warning from a crawling tool is a real problem; the important findings are those matching what Google actually sees. The main areas examined during a website audit are:
| Field | What is checked | Data consulted |
|---|---|---|
| Server and response codes | 5xx errors, 404 and soft 404 pages, addresses blocked with 403 | Crawl output, Search Console |
| robots.txt | Important pages or CSS and JavaScript files blocked accidentally | robots.txt report, URL Inspection |
| Indexing rules | Forgotten noindex tags, X-Robots-Tag headers | Page source, HTTP headers |
| Canonical | Self-referencing canonical tags, conflicting signals, parameterized duplicates | Crawl output, URL Inspection |
| Redirects | Permanent moves left as 302s, chains, and loops | Crawl output |
| Sitemap | Including only canonical URLs returning 200 that are intended for indexing | Sitemaps report |
| Internal links | Pages receiving no links, broken links, and links to duplicate URLs | Crawl output |
| Page experience | LCP, INP, and CLS values, mobile appearance, HTTPS | Core Web Vitals report, PageSpeed Insights |
| Structured data | Incorrect markup or markup describing content invisible on the page | Rich Results Test |
Findings are prioritized by impact: errors preventing indexing are addressed first, followed by adjustments improving crawl efficiency and page experience.
What do indexing statuses in Search Console mean?
The Page indexing report in Search Console separates URLs known to Google into indexed and unindexed groups and gives a reason for those not indexed. Google’s Page indexing report help page emphasizes that not being indexed is not always an error: pages marked noindex, duplicates of another page, or pages unsuitable for indexing such as filter versions are expected to remain excluded. Common reasons and corresponding actions are:
| Status in the report | Meaning | Action taken |
|---|---|---|
| Server error (5xx) | The server returned an error when the page was requested | Server logs are used to identify the plugin or query causing the error |
| Redirect error | An excessively long chain, loop, or broken destination | Redirects are rewritten so they reach the final address in one step |
| URL blocked by robots.txt | Googlebot does not have permission to crawl the page | If the page should be indexed, the rule is removed; if not, the block is removed and noindex is used |
| URL marked “noindex” | A noindex rule was found on the page | If unintentional, it is removed from theme, plugin, or SEO plugin settings |
| Soft 404 | The page returns 200 but looks like a “not found” page | Nonexistent pages return 404 or 410, while pages with thin content are strengthened |
| Crawled – currently not indexed | Google crawled the page but did not index it | Content originality, internal links, and possible duplication are assessed |
| Discovered – currently not indexed | Google knows the URL but has not yet crawled it | Server load, the number of low-value URLs, and internal linking structure are examined |
| Duplicate, Google chose different canonical than user | A different URL was selected instead of the specified canonical | Content differences between pages and the consistency of canonical signals are checked |
| Page with redirect | The URL redirects to another address | Usually no action is needed; internal links are updated to the final address |
Within technical SEO services, once all instances of an issue are corrected, a validation request is sent to Google through the report and affected URLs are checked again.
How should robots.txt, noindex, and sitemaps be used correctly?
robots.txt controls crawling, noindex controls indexing, and sitemaps support discovery; the three cannot substitute for each other. According to Google’s documentation, robots.txt is not a tool for hiding a page from search results: if another source links to a blocked URL, the address may appear in results without a description.
For a noindex rule to work, the page must be crawlable. On a page both blocked by robots.txt and carrying noindex, Googlebot never sees the rule. The Search Console warning “Indexed, though blocked by robots.txt” appears when other sources link to a blocked page; Google’s recommended solution is to remove the block and use noindex.
A sitemap tells Google which URLs are considered important but does not guarantee they will be crawled. Google states that websites with good internal links and approximately 500 or fewer pages may not need a sitemap, while large, new, or media-heavy websites benefit from one. WordPress generates a sitemap automatically; the audit checks its accuracy. The correct uses of the three tools are:
- robots.txt: Areas not worth crawling, such as the administration panel, internal search results, and endless filter combinations
- noindex: Pages that can be crawled but should not appear in results, such as thank-you pages or tag archives with thin content
- Sitemap: An up-to-date list of canonical URLs intended for indexing, including lastmod information for changed pages
Duplicate content, canonical tags, and redirect chains
Duplicate content means publishing identical or very similar content at multiple URLs; Google then selects one URL in the group as canonical. Common sources on WordPress websites include HTTP and HTTPS versions, www and non-www versions, addresses with and without trailing slashes, advertising-parameter URLs, and identical category and tag archives.
Google’s guide to specifying a canonical URL ranks methods of expressing a preference by strength: redirects and rel=”canonical” are strong signals, while sitemap inclusion is weak. The same guide recommends avoiding robots.txt or noindex for canonicalization, adding a self-referencing canonical to each canonical page, and always linking internally to the canonical URL. When the canonical points to one address and the sitemap to another, signals conflict and Google may make its own choice.
Redirect chains and loops
A redirect chain means an old address reaches its final destination through several intermediate redirects: the HTTP version goes first to HTTPS, then to www, and finally to the new page. Google’s crawlers follow up to 10 redirect hops by default, and the crawl budget guide states that long chains negatively affect crawling. In a loop, two addresses redirect to each other and the page never opens.
The solution is for every old address to reach its final destination in one step and for internal links to be updated directly to the final address. 301 or 308 is used for permanent moves and 302 for temporary situations; leaving a permanent move as a 302 can cause Google to keep showing the old address in search results. For domain or infrastructure changes, the redirect map is prepared from the outset as part of the WordPress site migration process.
Let’s identify why your pages are not indexed
Once read access to Search Console is granted, reasons in the indexing report are examined individually using example URLs. Which issue should be resolved first and the scope of work are discussed based on this review.
How do crawling and rendering work on websites using JavaScript?
Google can execute JavaScript, but it first crawls the page, then places it in the rendering queue, and indexes the rendered HTML; if content appears only after JavaScript runs, waiting in this queue adds to the process. Google’s JavaScript SEO basics documentation still considers server-side rendering or prerendering a good idea because it makes websites faster and not every bot can execute JavaScript. The audit checks:
- Links use actual link tags with href attributes; menus operating only through click events may not be crawlable.
- Canonical and title information are present in the initial HTML; JavaScript does not replace these values with a different URL or title.
- In single-page applications, nonexistent content is redirected to an address where the server returns 404, or noindex is added to the page; this prevents soft 404s.
- JavaScript and CSS files needed to render the page are not blocked by robots.txt.
- The live test in URL Inspection is used to check the HTML Googlebot sees.
Core Web Vitals: recommended values for LCP, INP, and CLS
Core Web Vitals are three metrics measuring page experience through loading, interaction, and visual stability. According to the Core Web Vitals guide on web.dev, recommended targets for a good experience are LCP (Largest Contentful Paint) no later than 2.5 seconds after the page begins loading, INP (Interaction to Next Paint) of 200 milliseconds or less, and CLS (Cumulative Layout Shift) of 0.1 or less.
The targets are recommended at the 75th percentile of page loads, with mobile and desktop assessed separately. Search Console’s Core Web Vitals report shows real-user data; laboratory measurements in PageSpeed Insights help identify causes, and the two datasets do not always produce the same result.
The audit within technical SEO services reveals which page template falls behind on which metric and whether delay originates from the server, images, or heavy scripts. On WordPress websites, practical speed corrections are performed through the speed optimization and performance improvement service; no speed score guarantee is given.
Structured data validation and hreflang checks
Structured data describes page content to Google in a standard format and provides eligibility for certain search features; Google recommends JSON-LD in most cases. During the audit, markup is checked with the Rich Results Test, critical errors are corrected, and rich result reports in Search Console are monitored after launch.
Two rules are often overlooked: content invisible to readers on the page must not be marked up, and Google does not guarantee rich results even when markup is correct. Details of LocalBusiness markup used for local businesses are explained on the local SEO services page.
hreflang: a brief check for multilingual websites
hreflang tells Google about different language or regional versions of the same page and is used only when genuinely translated versions exist. Checks cover each version listing itself and the other versions, reciprocal links, correct language codes, x-default for unmatched languages, and each version’s canonical tag pointing to its own language page.
Which websites need crawl budget work and log analysis?
Crawl budget is not a problem for most websites. Google’s crawl budget guide describes itself as an advanced resource and says it is written for roughly three website types: large websites with over 1 million unique pages and content changing weekly; medium and large websites with over 10,000 pages and content changing daily; and websites where most URLs are reported as discovered but not yet indexed. For other websites whose pages are crawled on their publication day, keeping the sitemap current and checking the indexing report regularly is sufficient.
With filter and sort options generating thousands of URLs, e-commerce websites can approach this threshold more easily. Practices highlighted in the guide are:
- Consolidating duplicate content and blocking the crawling of unimportant URLs with robots.txt
- Avoiding noindex for crawl budget management; Google still requests a page carrying noindex
- Returning 404 or 410 for permanently removed pages and correcting soft 404 errors
- Keeping the sitemap current with lastmod information and avoiding long redirect chains
- Improving server response time; according to Google, fast and stable responses can increase the crawl capacity limit
Log analysis shows which URLs Googlebot requests, how often, and with which response codes in server access logs. For large websites, these logs reveal whether crawling is spent on parameterized duplicates, old redirects, or error pages; the Crawl stats report in Search Console offers a more condensed view. Small and medium corporate websites generally do not need log analysis.
The difference between an automated crawl report and a practical technical audit
In common practice, technical SEO services may amount to forwarding a crawling tool’s hundreds of warning rows unchanged. In these lists, a noindex error cutting off traffic and a negligible warning appear equally important, leaving it unclear which should be solved first.
In a practical audit, each finding is matched to the actual situation in Search Console, prioritized, and corrected at its source: noindex added by a plugin is removed through its settings, and a duplicate URL generated by a theme template is corrected in the template itself. After correction, URL Inspection is used for validation, and every change is documented in a reversible form.
Technical SEO process, scope, and quotation
Technical SEO services begin with obtaining access and finish with corrections verified on Google’s side.
How does the process proceed?
- Initial meeting: The website’s infrastructure, the problem experienced, and recent changes (migration, theme change, new plugin) are discussed.
- Access: Read access to Search Console is granted first; administration panel and hosting access are configured securely if required.
- Crawling and data matching: The website is crawled; findings are compared with Search Console, Core Web Vitals, and server logs when needed.
- Report and priorities: Issues are ranked by impact, and a proposed solution is written for each one.
- Implementation: Approved corrections are performed after a backup; no unapproved changes are made on the live website.
- Verification: URL Inspection and report validations confirm that Google has seen the corrections.
What determines the quote?
When technical SEO is conducted as part of monthly SEO services, fees start at 9,000 TL per month; no fixed price is published for a one-time technical review, and a firm quote is shared after examining the website. In Istanbul, Onur Freelance can meet in person in Maltepe Gülsuyu if preferred and works remotely in other cities; WhatsApp and phone contact are available between 09.00–21.00. The main factors affecting the quote are:
- Page count and structures generating URLs (filters, internal search, parameters)
- Infrastructure: WordPress, WooCommerce, custom software, or a JavaScript framework
- The prevalence of issues in Search Console and whether server logs are accessible
- Whether corrections are to be reported only or also implemented
- Whether additional work such as migration, speed adjustments, or hacked website cleanup is needed
Let’s put your technical infrastructure on a solid foundation
The same contact line can be used to discuss why a single page is not indexed or a comprehensive audit for the entire website; if implementation of identified corrections is requested, the work plan is finalized after the initial review.
Who carries out the work? Technical SEO audits and corrections are performed by the team the business communicates with directly; the working model and considerations when choosing a specialist appear on the freelance SEO specialist page.
Related guides
Frequently asked questions
What do technical SEO services cover?
Technical SEO services cover crawl access, indexing rules, canonical tags and redirects, sitemaps, JavaScript rendering, Core Web Vitals, and structured data checks. The aim is for Google to find and index important website pages without problems.
Are technical SEO analysis and a website audit the same thing?
They largely describe the same work: a website audit involves crawling the website and identifying technical findings, while technical SEO analysis also includes interpreting and prioritizing these findings using Search Console data. Implementing findings is planned as a separate stage.
What does "Crawled - currently not indexed" mean in Search Console?
It means Google has crawled the page but has not indexed it; the page may or may not be indexed later. In this situation, content originality, internal links, and whether the page duplicates another page are examined; the URL does not need to be resubmitted.
Can robots.txt hide a page from Google?
No. robots.txt blocks crawling, but a URL linked from elsewhere can appear in results without a description. To keep the page out of results, leave it crawlable and use noindex, or protect it with a password.
Is crawl budget important for a small corporate website?
Generally, it is not. Google’s crawl budget guide targets very large or frequently updated websites; for small websites, a current sitemap and regular checks of the indexing report are sufficient.
Does reaching Core Web Vitals targets guarantee rankings?
No. Core Web Vitals are one measure of page experience, and reaching the targets supports a good experience, but rankings depend on many factors. No speed or score guarantee is given.
How long do technical SEO corrections take to produce results?
Timing varies from page to page; the effect depends on Google recrawling the relevant pages. Google states that noticing a change such as noindex can take months depending on a page’s importance; recrawling important pages can be requested through URL Inspection.
How is technical SEO pricing determined?
Pricing depends on page count, infrastructure, the prevalence of issues in Search Console, whether corrections will be implemented, and the need for additional work. A firm quote is provided after examining the website rather than using a fixed package.
Call us
Call us for detailed information.
Let us call you!
Share your number and let us call you!
Our other services
- › Corporate web design
- › E-commerce website development
- › SEO optimization
- › WordPress website development
- › Google advertising management
- › WordPress speed optimization
Service areas
- › Web design in Sakarya
- › Web design in Tekirdağ
- › Web design in Bursa
- › Web design in Beşiktaş
- › Web design in Şişli
- › Web design in Tuzla
- › Web design in Ümraniye
- › Web design in Kadıköy
- › Web design in Istanbul
- › Web design in Ankara
- › Web design in Ataşehir
- › Web design in Üsküdar
- › Web design in Kartal
- › Web design in Maltepe
- › Web design in Pendik
- › Web design in Kocaeli
- › Web design in İzmir
- › Web design in Antalya
