A new website with no traffic after a month needs a diagnosis: can Google find its important pages, has it indexed them, are they receiving relevant impressions, and are visits being measured correctly? A month without traffic does not establish a penalty or a fixed new-site waiting period. Waiting longer will not repair an accidental noindex setting or a broken enquiry form.
The following five tasks turn that broad complaint into page-level decisions. Start with confirmed faults that stop access or customer actions, then work on search demand, content and the site's supporting structure.
1. Set up Search Console and inspect the pages that matter
Google can discover a website through links without its owner registering for Search Console. Verification gives you access to your site's data and diagnostic tools; it is not an indexing prerequisite. Google's explanation of how Search works separates crawling, indexing and serving results, none of which is guaranteed for every URL.
Choose the property and submit the real sitemap
- Record the production address, including HTTPS and the preferred hostname. A URL-prefix property covers the specified prefix; a Domain property has broader coverage and requires DNS verification. Choose a scope you can verify and that covers the URLs you need.
- Use an available ownership verification method. Check that an HTML verification file is publicly accessible at its required location, or that the DNS record is correct. Retain the verification token afterward. DNS changes do not all finish within a fixed ten-minute window.
- Open the sitemap your CMS actually generates. Check its contents, not just its filename, then submit it through the Sitemaps report. Avoid installing a second generator just because a tutorial uses another path.
- Inspect the homepage, priority product or service pages, and representative articles separately. An indexed homepage is not proof that all important pages are indexed.
A sitemap helps discovery; it does not order Google to index pages or give them priority. Submission, successful reading and URL indexing are separate results.
Use the reported state to choose the next action
| State | What to investigate | Useful next action |
|---|---|---|
| URL unknown to Google | Public availability, sitemap inclusion and links from relevant pages | Provide a working discovery path and request indexing where appropriate |
| Discovered, not yet crawled | Server reliability, page importance and excessive duplicate or unwanted URLs | Fix confirmed problems and monitor actual crawl information |
| Crawled, currently not indexed | Rendered content, canonical selection, duplication and the page's distinct purpose | Review the page rather than infer a plagiarism finding or penalty |
| Unintended exclusion or access failure | noindex, robots rules, authentication, HTTP responses and CDN controls | Repair the responsible configuration and retest |
| Indexed without relevant impressions | Search demand, language, intent, competing answers and available data | Investigate the content and query match |
URL Inspection reports indexed information and also offers a live test. A successful live test does not establish current indexing or predict Google's canonical choice. A normal browser receiving HTTP 200 does not prove Googlebot receives the same content. Meeting Google's minimum technical requirements makes a page eligible, not guaranteed to rank.
2. Repair slow or unusable customer journeys
On a phone, open a priority page, read its specifications, expand its details and submit an enquiry. Look for clipped text, obstructed controls, unstable images and forms without a clear successful result. These are concrete tasks to fix, rather than reasons to chase every plugin suggestion.
Separate PageSpeed Insights field data from Lighthouse lab results. The good Core Web Vitals thresholds are LCP at or below 2.5 seconds, INP at or below 200 milliseconds, and CLS at or below 0.1, assessed at the 75th percentile for field experience and segmented by mobile and desktop. New sites may lack sufficient field data. Missing data is not a pass, and lab TBT is not a substitute for field INP.
- Slow main image: identify the actual LCP element before changing compression, dimensions or loading priority. Do not apply lazy loading indiscriminately to above-the-fold content.
- Unresponsive interactions: inspect long tasks and the components that cause them. Removing customer support or conversion tracking without checking its purpose can break the business journey.
- Layout shifts: reserve appropriate space for images and asynchronous components. A shifting enquiry button may deserve attention before a smaller loading improvement.
- Horizontal overflow: repair the table, code block or positioned element causing it. Hiding overflow while cutting off information is not a successful fix.
Prioritize severity, coverage and reproducible causes, then retest under comparable conditions. There is no published ranking-weight formula that assigns half the work to LCP and treats CLS as unimportant.
3. Make the important pages answer actual customer questions
Write down the task a visitor needs to complete. Someone checking whether a part fits an existing assembly needs compatible models, dimensions, conditions and exclusions. A company history or a page full of “premium quality” claims does not answer that question.
Use customer enquiries, available Search Console queries, target-language results and reliable research tools to identify questions. A long-tail keyword is not automatically easy or commercially valuable. Check search intent against the actual results: an installation query calls for usable instructions, while a selection query needs a comparison with meaningful criteria.
- Read representative competing answers and identify missing decisions, evidence or practical steps.
- Add information you can substantiate: product details, model differences, documented processes and accessible supporting material.
- Place qualifications next to the conclusion they limit. A source must support the specific statement, not merely have a well-known brand.
- Use a clear title and answer promptly. Let the subject determine the length and structure.
- Check authorship and case-study claims. Describe an example as an example; do not invent a customer test or an expert biography.
Google's helpful-content guidance does not specify a preferred word count and discourages changing dates without substantial updates. An absent query in Search Console is not proof of zero demand. Avoid splitting one answer into several near-identical posts simply to raise the article count.
4. Connect the pages and plan external link support
Give useful new pages a relevant path from existing content or navigation. Explain the destination in the anchor text: “installation dimension checklist” is more informative than a repeated “click here.” Google's link guidance says there is no magical ideal number of links; pages you care about should have a link from another page on your site.
For external links, Guangsuan's combination strategy emphasizes scale, a mix of resource types and tiered construction, with on-site content as the foundation. GPB provides one original related article on one independent domain for each link. GNB focuses on a single site's homepage and brand anchors, while GMB extends external coverage across a target URL list. Choose the scope, budget and delivery checks based on the site's actual needs.
These are Guangsuan's service methods, not a Google-mandated daily link quota for new sites. A DA threshold, a fixed anchor-text percentage or a platform name is not an official safe line, and a made-up growth example cannot validate a forecast.
The Search Console Links report is a sample rather than an exhaustive list. It does not say whether links are nofollow. A reported link, an indexed source page and rankings for the destination are separate observations. State the limits of any public indexing check when you do not own the source property.
5. Keep a review record that leads to the next decision
For each priority URL, record the problem, dated evidence, change, release date and subsequent observation. Technical repairs can be retested immediately. Search outcomes require recrawling and enough comparable data; a universal 48-hour result or 90-day recovery promise is not a useful substitute.
| Observation | Next check | Unsupported shortcut |
|---|---|---|
| Relevant impressions appear | Review queries by page, country and device | Calling impressions qualified enquiries |
| Impressions but few clicks | Inspect position distribution, query mix, result features and title accuracy | Applying one CTR cutoff to every query |
| GSC clicks but few GA4 visits | Check dates, time zones, attribution, consent and tracking | Expecting one-to-one equality or diagnosing a penalty |
| Visits but no enquiries | Test forms and assess audience fit, product information and the next action | Assuming more posts will fix conversion |
Use the Search Console Performance report for search impressions and clicks, and use analytics plus actual business records for visits and qualified enquiries. Keep small-sample fluctuations provisional.
A Screaming Frog crawl can help locate broken internal paths and response errors. Redirect genuine replacements to their corresponding destinations; do not send every missing URL to the homepage. Correct obsolete facts and broken journeys when found, rather than updating a date to simulate activity. Guangsuan's SEO delivery approach connects technical, content and external-link work around defined pages and deliverables, so the next review can establish what was actually repaired.