Google Search Console Setup for a New Website: A Practical SEO Checklist
A new website should be connected to Google Search Console before you start judging its SEO performance. The setup is straightforward: add the correct property, verify ownership, confirm that important pages are accessible, submit the sitemap if you have one, and establish a baseline in the Performance report. Search Console can reveal how Google crawls, indexes, and displays a site, but it cannot guarantee indexing, rankings, traffic, or a particular position.
For a business in Bangladesh or Dhaka, this first-party diagnostic is more useful than guessing from a personalised Google search. It shows evidence about your own property, including queries, pages, countries, devices, impressions, clicks, click-through rate, and average position. You can then use that evidence to improve the ArtX SEO services, content, or web development work that needs attention.
Quick Answer: How Do You Set Up Google Search Console for a New Website?
The short answer: Add your website as a Search Console property, choose a verification method you control, and wait for Google to collect data. Then inspect the homepage and one important service page, check the Page indexing report, submit the canonical sitemap URL, and record a baseline in the Performance report. Use URL Inspection to diagnose specific pages, not as a promise that a page will rank.
A sensible first session has five steps:
- Choose a property that covers the URLs you actually operate.
- Verify ownership without removing the verification token later.
- Test the public homepage and key pages with URL Inspection.
- Submit a clean sitemap containing the canonical URLs you want discovered.
- Review impressions and clicks over time instead of relying on a manual search from one device or location.
1. Choose the Right Search Console Property
Search Console offers two useful ways to represent a site. A Domain property covers all protocols and subdomains under a domain, while a URL-prefix property covers only the exact prefix you enter. Google’s ownership documentation notes that domain-provider verification is the method used for a Domain property. A URL-prefix property can use methods such as an HTML file, an HTML tag, Google Analytics, or Google Tag Manager when the requirements for that method are met.
For example, a Domain property for example.com is designed to include variations such as http, https, www, and other subdomains. A URL-prefix property such as https://www.example.com/ is narrower. That difference matters during a migration, when a site has a staging subdomain, or when the production site uses both www and the apex domain.
Before adding anything, write down the canonical production URL. Confirm that it redirects consistently, uses HTTPS, and does not expose a staging or preview hostname as the public version. If your Bangladesh business serves users from Dhaka and elsewhere, the property should still represent the actual production site rather than a location-specific assumption.
2. Verify Ownership Safely
Ownership verification is not a cosmetic setup step. A verified owner can access sensitive Search data and make changes that affect how a site is handled in Google services. Use the method that matches your access and hosting arrangement:
- DNS verification: useful for a Domain property, but it requires access to the domain provider.
- HTML file upload: place the exact file supplied by Google at the required public URL.
- HTML tag: add the exact meta tag to the page Google checks for the property.
- Google Analytics or Tag Manager: use an existing, correctly configured account when the verification conditions are satisfied.
Do not copy an example token from a tutorial. Use the exact token generated for your property. After verification succeeds, keep the DNS record, file, or tag in place. Google periodically checks whether the verification token is still valid, and access can expire if it is removed. Google also supports multiple verification methods, which can provide a recovery path if a deployment later removes one token.
If a developer or agency is helping with setup, give that person the appropriate Search Console user permission instead of sharing the Google account password. Keep ownership with the business or site operator. This is especially important during a website redesign or vendor change.
3. Run a First URL Inspection
Start with the homepage, then inspect one page that represents a real business goal, such as a web development service or a Dhaka location page. Enter the complete URL in URL Inspection and read the indexed result first. That result describes Google’s most recently indexed version, not necessarily the HTML currently live in the browser.
Next, use Test live URL after checking that the page is publicly reachable without a login. The live test can help you investigate whether Google’s inspection tool can fetch the page, view loaded resources, and render the content. It is useful for finding an accidental noindex, a crawl block, a server response problem, or a page whose important content is missing from the rendered output.
Keep the two results separate in your notes:
- Indexed result: what Google last stored and used as index information.
- Live test: what the inspection tool can fetch from the current public page.
A live test does not check every indexing condition. It does not prove that a duplicate page will be indexed, that quality requirements are met, or that a page will appear for a query. Similarly, the status “URL is on Google” means the URL is eligible to appear; it is not a ranking or appearance guarantee.
If you have fixed a specific page and it is eligible, you may use Request indexing for that URL. Treat this as a crawl request, not a publication button. Google documents daily limits and explains that requesting indexing does not guarantee inclusion. For many changed URLs, a correctly maintained sitemap is the more scalable signal.
4. Submit a Clean Sitemap
A sitemap helps Google discover the URLs you want considered. It should contain fully qualified absolute URLs, such as https://example.com/services, rather than relative paths. Include the canonical production URLs that you want in search. Do not use the sitemap as a dumping ground for staging pages, redirecting URLs, blocked pages, or duplicate variants.
Google supports XML, RSS or Atom, and text sitemap formats. XML is the most flexible when you need to describe images, videos, or localized versions. A CMS may generate a sitemap automatically; for a small site, a manual file can be manageable; for a growing site, generating it from the content system reduces drift.
You can submit the sitemap in the Search Console Sitemaps report or reference it in robots.txt. Submitting a sitemap is only a hint. It does not guarantee that Google will download it, crawl every listed URL, index the pages, or show them in search. If you use <lastmod>, keep it accurate and tie it to a meaningful page update rather than changing it on every deployment.
Google’s documented limit for one sitemap file is 50 MB uncompressed or 50,000 URLs. Larger sites need multiple sitemap files and can use a sitemap index. Most small businesses in Bangladesh will not approach that limit, but the same rule is helpful when an e-commerce catalogue or a multi-location site grows.
For a practical content architecture, connect the sitemap with crawlable internal links. A guide such as How to build an SEO-ready website in Bangladesh should lead readers to the relevant service, contact, or pricing page. Discovery should not depend on a single submitted file.
5. Establish an Evidence-Based Baseline
The Search results Performance report is the place to record the starting point. Google exposes four core metrics: clicks, impressions, click-through rate (CTR), and average position. You can group the data by queries, pages, countries, devices, search appearance, or dates.
For a new website, early data may be sparse. That is not a reason to invent a benchmark or promise a date when rankings will arrive. Record the date of setup, the pages submitted, and the first available observations. After enough data accumulates, ask practical questions:
- Which service or location pages receive impressions but few clicks?
- Which queries describe an audience that the page does not answer clearly?
- Are mobile users reaching the same useful content as desktop users?
- Did a redesign, URL change, or content update coincide with a traffic change?
- Which pages earn impressions but need better titles, descriptions, internal links, or clearer next steps?
Search results vary by time, location, device, and recent history. A manual search from a Dhaka office, a phone on a mobile network, and a logged-in browser is not a reliable substitute for the property’s report. Use the report to find patterns, then inspect the actual page and the user journey.
A Weekly and Monthly Operating Routine
A lightweight routine is enough for most small and medium websites. After a launch or major content change, inspect the affected URLs, check the sitemap status, and review the Page indexing report for new exclusions or errors. Once the site is stable, review Search Console roughly monthly and whenever the content, templates, domain, or URL structure changes.
Pair Search Console with a content review. A page that earns impressions but no qualified actions may need a clearer answer, stronger evidence, or a better service path. A page that is not indexed needs technical and content diagnosis before you publish several near-duplicates. The ArtX work and case studies can help a team assess how design, development, and search requirements fit together, but the right next step should come from the site’s actual data.
Do not treat Search Console as a ranking scoreboard alone. Its value is diagnostic: it connects Google’s view of crawling and indexing with the questions people use and the pages they reach. That makes it a useful feedback loop for a new website, including one built for a Bangladesh or Dhaka audience.
Frequently Asked Questions (FAQ)
Does Google Search Console make a new website rank faster?
No. Search Console helps you understand crawling, indexing, and Search performance. Verification, sitemap submission, and indexing requests do not guarantee crawling, indexing, traffic, a featured result, or a particular ranking position. Use the tool to find problems and measure change, while the site still needs useful content and a sound technical foundation.
Should I use a Domain property or a URL-prefix property?
Use a Domain property when you want coverage across the domain’s protocols and subdomains and you can verify through the domain provider. Use a URL-prefix property when you need a narrower scope, such as one HTTPS host or path. The best choice depends on the URLs your team owns and manages.
How long does Search Console take to show data?
Google says data can take a few days to start accruing for a newly added property. The amount and freshness of data varies by report. Do not interpret an empty early report as proof that the website has failed, and do not replace the report with unsupported traffic estimates.
Should I request indexing for every page?
No. Request indexing is intended for a specific URL after you have checked and fixed it, and Google applies daily limits. For many new or updated pages, maintain a sitemap with canonical URLs and build crawlable internal links. Neither method guarantees inclusion in Google’s index.
Can Search Console tell me why a page is not ranking in Dhaka?
It can provide useful evidence about indexing, queries, pages, countries, devices, and search performance, but it cannot explain every ranking factor or reproduce one person’s results. Inspect the page, compare its intent and usefulness with the query, and account for location, device, competition, and recent changes before drawing a conclusion.
Sources
Written by Priya Nair
SEO & Growth Strategist, ArtX at ArtX
ArtX is an independent studio founded in 2016 in Bangladesh, engineering high-craft digital products, custom e-commerce stores, and high-ranking SEO strategies for brands worldwide.
Need this implemented for your website?
Talk directly with our senior engineers and get a tailored strategy.