SEO audit + website indexing acceleration plan (23,000+ pages)

Greetings

My name is Vyacheslav, I am an SEO specialist with 5 years of experience in promoting websites from various niches. Your project caught my attention because I have helped similar projects achieve sustainable traffic growth and improve their positions in search engines.

What I can offer:
- Website audit: analysis of current optimization, technical errors, and content.
- Keyword research: researching and selecting relevant key phrases to improve visibility.
- On-Page optimization: adjusting meta tags, internal linking, loading speed, and other factors.
- Content strategy: suggestions for improving existing content and creating new content focused on key queries.
… - Off-Page optimization: developing a strategy for acquiring external links to increase the site's authority.
- Analytics and reporting: monthly reports on results and metrics to track effectiveness.

I would be happy to discuss your project in more detail to assess the current tasks and select optimal promotion methods for your niche. If you are interested in my approach, I can provide examples of successful projects.

Show original

Translate

👋 Hello. My portfolio - Freelancehunt

I would start with Google Search Console - I would check which pages exist but are not indexed, and what group they are in (discovered / crawled, but not indexed).

💼 Next, I would check the sitemap, robots.txt, and canonical - often there are either duplicates or something that hinders normal indexing.

Tools: GSC, Screaming Frog, Ahrefs, sometimes server logs.

⏰ Deadline - 14 days.
… 💵 Budget - 27000 UAH.

🚀 I take every project seriously and work for results. I don't just close tasks, but bring the work to a state where the product looks high-quality, professional, and instills trust in clients.

Show original

Translate

👋 Hello, the largest and most interesting projects — Freelancehunt

My name is Ilya, an SEO technical specialist with experience working with large content sites (from 10k to 100k+ pages).
My work plan for your site (23,000+ pages):

What I will start the diagnosis with:
Deep analysis of Google Search Console (Crawl Stats, Indexing reports, "Discovered — not indexed", Page Indexing)
Checking Cloudflare settings (Caching, Crawler Hints, Robots.txt, Sitemap)
Technical audit: canonicals, hreflang, lastmod, internal linking, URL structure
… Analysis of server logs (if access is available)

The most common reasons for slow indexing on new domains with a large number of pages:
Limited Crawl Budget (Google simply can't keep up)
Weak internal linking and low PageRank of new pages
Problems with Cloudflare (aggressive caching, bot blocking)
Incorrect lastmod / sitemap
Thin/duplicate content that Google doesn't want to spend budget on

Specific steps that will have the greatest effect:
Optimization of sitemap + splitting into several (index sitemap)
Improvement of internal linking (especially to new pages)
Configuration of Cloudflare Crawler Hints + Page Rules
Prioritization of the most important pages
Creation of additional hub pages and clusters
Constant monitoring and "warming up" of indexing

Tools:
Google Search Console + Google Analytics 4
Screaming Frog, Sitebulb
Cloudflare Dashboard + Logs
Ahrefs / Semrush (for analysis)
Looker Studio for reporting

Cost: 27,000 UAH
Deadline: 14 days
Ready to conduct a full audit and detailed action plan already at the first stage.
What do you think of this approach? 👀

Show original

Translate

Hello! My name is Nikita, and I have been working in SEO for over 5 years. 🎯 During this time, I have brought dozens of websites to the top for competitive queries, worked with various niches, and have a good understanding of how search algorithms respond to changes. I don't just do optimization for the sake of it; I look at the website through the eyes of a search bot and a potential client at the same time. The technical part, content, links, all of this needs to work together; otherwise, there will be no results. If you're interested in discussing your project and understanding what hinders growth in organic traffic, I'm ready to talk.

Show original

Translate

Hello! I'm ready to get started.

I would begin with an analysis of Google Search Console: the statuses "Discovered, but not indexed" and "Crawled, but not indexed," after which I would check the crawl budget, canonical tags, sitemap, lastmod, robots.txt, and internal linking. For new large websites, the problem often lies in weak signals of page importance, the quality of internal links, and the structure of indexing. I use Google Search Console, Screaming Frog, PageSpeed Insights, Ahrefs/Serpstat, and Cloudflare analytics. After the audit, I will prepare a prioritized action plan and, if necessary, assist with its implementation.

Show original

Translate

Good day! 🧡
I am ready to start working and would be happy to help with minimal deadlines 😉
I have experience working on similar projects. 🌼 (I have reviews on this topic and work in my portfolio)
I will do it in the best way, starting now! 🚀🛸✈️

Feel free to write, we will discuss. I respond instantly!

Show original

Translate

Good day! Regarding your project (Nuxt + Cloudflare Pages, 23k+ pages, "discovered but not indexed") — this is a typical situation for projects of this scale; I have handled similar cases.

How I work: I conduct a full diagnosis on three levels — Google Search Console, crawl budget and Googlebot behavior on Cloudflare, and the technical foundation of the site. I draw conclusions based on REAL data from your site specifically, not from general advice — which is why the plan is tailored to your situation, not a template.

Result: an audit of the actual reasons for not being indexed specifically for you + a step-by-step plan with priorities (which will provide the largest increase in indexing the fastest). I am ready to implement it immediately.

To show specifics based on your numbers — please provide view access in GSC, and I will highlight the main reasons even before we start, so you can see that you are not taking a "cat in a bag."

Examples of work: Freelancehunt · https://guardlabs.online
…
Cost: 27,000 UAH, duration 7 days.

Show original

Translate

Hello, Pavlo! Very cool and lively job description, it's nice to see a clear understanding of the problem from the website owner. I like large structures, so I will respond directly to the essence of your request:
1. Where will I start the diagnosis?
Google Search Console (Coverage Analysis): We need to clearly divide the pages into two groups. What predominates: "Discovered, but not indexed" (problem with crawl budget or content quality) or "Crawled, but not indexed" (Google visited, looked, but decided that the page has no value for search).
Checking Nuxt rendering: Through "Live URL Inspection" in GSC, I will see if Googlebot sees all the text content and links, or if due to the specifics of the JavaScript framework it sees a blank screen.

Analysis of Sitemap and Canonical logic: Are the priorities and lastmod tags correctly set (so that the bot only sees updated pages and does not waste time on old ones)?
2. Why is a new domain with 23k+ pages being indexed slowly?
Low trust level and Crawl Budget limit: Google does not yet know your site. It allocates very little time per day (for example, it is only willing to crawl 200 pages). If the bot encounters duplicates, empty pages, or technical junk during these visits, it simply leaves without reaching useful content.

… Internal linking (Site Depth): If a page is more than 3-4 clicks away from the homepage and there are no internal links from other articles to it, Googlebot considers it unimportant and puts it in a long drawer.
3. What will have the biggest effect right from the start?
Implementing Google Indexing API: Since you are in a financial/review niche (where content needs to be current), the standard indexing queue is too long. Setting up the API will allow sending new pages to the index in batches automatically.
Optimizing internal linking: Creating cross-cutting dynamic blocks (for example, "Latest Reviews", "Popular") to pull deep pages up.
Breaking down Sitemap.xml: A large sitemap with 23k pages needs to be broken down into smaller parts (up to 5000 URLs in one) to ease the crawler's work.
4. Tools:
For analysis and semantic collection, I use Google Search Console, Screaming Frog, and Ahrefs.
Pavlo, I will prepare the technical part of the audit, and implementing changes (especially regarding Nuxt and Cloudflare) is best done in tandem with your developer, to whom I will provide clear specifications. If this approach resonates with you — let's discuss it in more detail in the chat!

Show original

Translate

Often, the problem with site indexing arises from incorrectly configured crawl budget and poor XML sitemap structuring. I will start by analyzing Googlebot's behavior using Search Console data: I will check the ratio of discovered/indexed, the speed of page crawling, and the presence of blocks in robots.txt.

For Nuxt projects, the stability of SSR rendering is critical—Googlebot may ignore AJAX links. I will use Sitebulb and Screaming Frog to check internal linking, as well as Ahrefs to identify errors in sitemaps and duplicate content.

I propose three steps: 1) Correct the priorities in the XML sitemap considering lastmod; 2) Configure a more dynamic crawl-delay in Cloudflare; 3) Create a hybrid indexing plan focusing on older pages. We will continue with optimizing canonical tags and headers.

Do you need access to Google Analytics or a matrix of incoming queries to identify content with the highest potential for indexing?

Show original

Translate

Hello, Pavlo!

Here is a selection of our case studies with results: https://www.newstart-digital.com.ua/#cases

— We will conduct a technical audit to identify the reasons for slow indexing and issues with crawl budget.
— We will provide a clear plan with specific steps to speed up indexing and improve rankings.
— We will suggest options for optimizing the sitemap, robots.txt, and internal linking.

I propose starting with a free SEO audit of your website to better understand the situation and offer a personalized action plan. Let me know when it would be convenient for you to discuss the details.

Show original

Translate

Good day! 👋
I have over 14 years of practical experience in SEO, having worked with online stores and large catalogs in Ukraine, Europe, and the USA.
Regarding your case (23,000+ pages on Nuxt + Cloudflare), from experience, the problem often lies in one or several areas:
🔹 Google does not see sufficient value in some pages and delays their indexing;
🔹 crawl budget is not used effectively;
🔹 issues with internal linking and page priorities;
🔹 nuances of SSR/rendering and what Googlebot actually receives;
🔹 sitemap, canonical, lastmod, or technical signals do not help Google determine indexing priorities.

… Here’s how I would start the diagnosis:
- analysis of Google Search Console (Coverage, Pages, Crawl Stats);
- checking the indexing logic of different types of pages;
- analysis of sitemap.xml and the actual inclusion of URLs in the index;
- checking internal linking and the depth of page nesting;
- analyzing how pages are seen by Googlebot after Nuxt rendering.

📌 The most common reasons for slow indexing on large sites after a domain change:
- ineffective use of crawl budget;
- insufficient internal weight of pages;
- issues with canonical;
- weak priority signals for Google;
- partial issues with SSR or JavaScript rendering;
- a large number of pages with low uniqueness or insufficient value for the search engine.

📌 What usually has the greatest effect:
- optimization of internal structure;
- improvement of linking;
- working with sitemap and indexing priorities;
- correct segmentation of page types;
- strengthening signals of importance for Google;
- working with the content of pages that do not get indexed.

🛠 Tools I use:
Google Search Console;
Google Analytics;
Serpstat;
Chrome DevTools;

I can show work cases in private messages. 📈
Message me privately — I will show cases and share my preliminary vision regarding your situation even before starting the work. 🤝

Show original

Translate

Good day! For projects with 23,000+ pages, the indexing issue is usually much deeper than just a sitemap or robots.txt. In such cases, I would start with analyzing data from Google Search Console: the ratio of "Discovered, but not indexed" to "Crawled, but not indexed," and I would also check how Google crawls the site and which URLs it spends crawl budget on.

I would pay special attention to the structure of internal linking, sitemap segmentation, canonical, lastmod, rendering Nuxt pages for Googlebot, and page quality signals. On large sites, these aspects often become the reason why thousands of pages remain out of the index for months.
For analysis, I use Google Search Console, Ahrefs, Serpstat, etc. After the audit, you will receive not general recommendations, but a specific action plan with priorities that will have the greatest impact on the speed of indexing and further growth of organic traffic.

I love complex technical projects and large site structures where it is important to understand the cause rather than fight the consequences.
Best regards, Daria! :)

Show original

Translate

Good day!
A case with a large number of pages https://freelancehunt.com/showcase/work/keys-seo-mizhnarodne-prosuvannya-turistic

What I would start the diagnosis with:
1. Google Search Console
I would check not the total number discovered but not indexed, but the distribution by URL types:

— which page templates are not indexed;
— which folders or sections fall into Discovered, currently not indexed;
… — are there Crawled, currently not indexed;
— are there duplicates without a selected canonical;
— which pages Google considers alternatives;
— is there a difference between URLs in the sitemap and actually indexed URLs.

2. Full site crawl
Analysis through Screaming Frog:
— statuses 200 3xx 4xx 5xx;
— canonical;
— noindex;
— robots directives;
— click depth;
— internal linking;
— orphan pages;
— duplicate title, h1, content;
— pagination;
— thin pages;
— soft 404;
— accessibility of important pages from HTML, not just from the sitemap.

3. Sitemap and lastmod
— do all URLs in the sitemap return 200;
— are there no noindex/canonical on other URLs;
— is the sitemap divided by page types;
— is lastmod real, not the same for all 23,000 URLs;
— does the sitemap not mix strong pages with weak mass templates.

Most often, I see the following reasons for slow indexing:
— new domain and immediately a very large volume of pages;
— Google does not see sufficient internal weight of the pages;
— pages are in the sitemap but weakly linked to each other;
— many similar pages with insufficient unique value;
— Google scans but does not see reasons to add everything to the index;
— important pages are too deep;
— incorrect canonicals or template duplication;
— weak hub/category page structure;
— no prioritization: Google receives 23,000 URLs without a clear hierarchy of importance;
— problems with rendering, caching, or headers on Cloudflare Pages.

What steps can yield the greatest effect:
1. Divide all pages into priority groups: those that have demand, traffic potential, internal links, and unique value.
2. Strengthen internal linking: hub pages, categories, thematic clusters, HTML sitemap, breadcrumbs, related content blocks.
3. Remove from indexing or not promote weak mass pages if they have no search value.
4. Redesign the sitemap: separate sitemaps by page types, priority URLs separately, correct lastmod.
5. Check page templates: uniqueness of title, h1, main content, FAQ, tables, internal links.
6. Check Cloudflare Nuxt: statuses, cache headers.

Show original

Translate

First, I will check the loading speed of your website. If the pages are visible to search bots but indexing is very slow, the problem may be that the content is generated on the client side. In such cases, Google indexes the pages with a separate bot, and this takes significantly more time.

It may be necessary to slightly modify the website's code to speed up indexing. Checking canonical, sitemap, lastmod, and robots.txt is needed, but they do not solve the problem of fast indexing. As can be seen, Google sees the pages — the issue is specifically with their processing by the bot.

Show original

Translate

Hello. I am interested in your project. I have over 10 years of experience in SEO. I have websites with more than 1,000,000 pages. Recently, regarding the phrase "discovered but not indexed," from my experience, it often indicates that Google does not want to index: Low-quality content (Thin Content), Duplicate content, Template content. Crawl budget indicates an ineffective structure of the site itself. There may be technical issues affecting this. Do you use SSR (Server-Side Rendering) or SSG (Static Site Generation)? All of this needs to be investigated. Also, if the site is new, you simply lack the authority for indexing such a large number of pages. Let's discuss the details in correspondence. To start, I propose the following work plan: Stage 1. Comprehensive audit and metric collection (Diagnosis) The primary task is to capture the current picture of the search bot's interaction with the resource and identify "bottlenecks" in the infrastructure.

Server behavior scanning: Analyzing log files and studying the Crawl Stats section in Google Search Console. This will allow us to assess the actual frequency of Googlebot visits and check if the response speed from Cloudflare limits the intensity of site crawling.

Index ratio: Monitoring the ratio between discovered and actually indexed pages to localize problematic areas.

Rendering validation: Testing Nuxt components through the URL Inspection tool to ensure that the bot receives full HTML code (SSR/SSG) and not an empty client template (SPA), which causes pages to "hang" in the queue.

Stage 2. Identification and classification of barriers (Causes) At this stage, factors that diminish the value of a large array of pages (23k+) in the eyes of algorithms are identified.
…
Crawl budget dispersion: Consumption of bot resources by technical junk, duplicates with navigation parameters, or template pages with low content uniqueness (Thin Content), which Google does not consider a priority.

Structural isolation (Orphan Pages): Lack of internal weight and excessive URL depth due to weak link architecture between pages.

Bot disorientation: Incorrect or cyclical canonical directives, random prohibitions in robots.txt/noindex, as well as the absence of relevant lastmod tags, forcing Google to recheck unchanged pages instead of crawling new ones.

Stage 3. Step-by-step technical optimization (Actions) Implementing targeted changes in the site's operation logic to facilitate and speed up its full scanning.

Restructuring site maps: Splitting the overall file.

Show original

Translate

Hello!

The diagnosis would start with:

GSC → "Indexing" section → "Discovered but not indexed" filter - this is the main indicator. With 23k pages, the first suspicion is always crawl budget: Googlebot simply cannot crawl all pages within a day.

The most common reasons on large sites:

Crawl budget is spent on junk URLs (parameters, duplicates, pagination without canonical), internal linking is weak, and Google cannot find deep pages due to the structure, lastmod in the sitemap is not updated or is set statically, Cloudflare aggressively caches and slows down crawl.
…
Specific steps with the greatest effect:

First - audit the sitemap: are all 23k URLs there, is the lastmod correct, are there any noindex pages in the sitemap? Second - crawl log analysis through Cloudflare or server logs to see the actual frequency of Googlebot crawls. Third - internal linking: hub category pages should link to all subpages, not just the top 20. Fourth - IndexNow for Cloudflare Pages (native support exists) - instantly notifies search engines about new/updated pages.

Tools: GSC, Screaming Frog for technical audit, Ahrefs/Semrush for crawl depth analysis, Cloudflare Analytics for crawl logs.

Show original

Translate

Good day! I was analyzing the indexing of such large sites when GSC shows "discovered but not indexed" on tens of thousands of pages.

I would start with two things. I would look at Crawl Stats to see how much Googlebot is actually crawling the site and whether it is hitting the response speed of Cloudflare. I would also check what the page is serving to the bot: on Nuxt, it often renders almost empty HTML without SSR or prerender, Google sees it as empty and keeps the page in the queue. This is the most common reason at such volumes along with the crawling budget, because 23k pages on a new domain, Google is simply not in a hurry to crawl, especially if many of them are thin or deeply hidden without internal links.

The technical part further: an honest lastmod in the sitemap, so as not to send to the queue what hasn’t changed, self-canonical without duplicates by parameters, robots and random noindex, and most importantly, interlinking to avoid orphans. For tools, this is GSC (indexing report plus Crawl Stats), Screaming Frog for crawling, server log analysis, and checking rendered HTML through URL Inspection.

I will compile a full audit with an action plan by priorities. Just let me know: is the site currently served in SSR/SSG or client-side rendering? This is what matters the most.

Show original

Translate

I would start not with general SEO advice, but with diagnosing how Google actually sees the site: I would check the status of pages in GSC, sitemap, robots.txt, canonical, noindex, duplicates, redirect chains, page response speed, internal linking structure, and whether 23,000 pages look like they are mass-generated or weakly connected to Google. Often, on large new sites, the problem is not just with the sitemap, but that Google sees many pages but lacks enough quality and importance signals: weak internal linking, identical page templates, few internal links to deep URLs, incorrect lastmod, duplication of meta/canonical, slow rendering of Nuxt pages, or incorrect content delivery for the bot. I use Google Search Console, Screaming Frog / Sitebulb, crawl depth logic, sitemap/robots checks, page template analysis, Cloudflare/Nuxt SSR/SSG checks, and manual audits of a sample of pages. As a result, I will provide not just an "audit," but a clear plan: what exactly hinders indexing, which pages should be prioritized for strengthening, how to restructure the sitemap, internal linking, canonical/lastmod, and which technical adjustments will have the greatest effect on speeding up indexing and improving rankings. If implementation is needed after the audit, I can also assist separately with the technical part on Nuxt + Cloudflare Pages.

Show original

Translate

The HighwayToTop team, we work with large websites.

1. Diagnostics — GSC: ratio of "discovered / not indexed", Crawl Stats, log files.
2. Reasons — crawl budget without priority, weak internal linking, issues with lastmod, canonical. We will separately check SSR rendering on Nuxt + Cloudflare and what Googlebot actually sees.
3. Steps — sitemap segmentation, strengthening links to priority pages, closing empty from crawling.
4. Tools — GSC, Screaming Frog, Ahrefs, server logs.

Message us privately — let's continue! 🙂

Show original

Translate

Hello. The hourly rate is 1300 UAH.
I will take the project on a monthly offer (minimum 6-9 months).
A young domain + many landing pages. I am not sure that unique content will be available for 23K pages in the financial niche. Just building domain trust.

My specialization is complex YMYL niches (finance) and large E-commerce projects. I have promoted such brands: easypay.ua, lovilave.com.ua, freelancehunt.com, isei.ua, krkr.com.ua.

Detailed case studies with graphs: Freelancehunt

Conditions: starting from 20 hours - 26000 UAH. Plus budget for text, links, services.

Show original

Translate

Good day! We have experience working with large content projects and know how to optimize the crawling budget for 23,000+ pages. We implement this through a technical audit of indexing, setting up the sitemap, optimizing internal linking, and eliminating duplicates. We will provide a detailed action plan for quickly getting pages into Google's search results.

Show original

Translate