Start by getting found, not by getting ranked. A new site has no crawl history, no links, and no trust. Google has to discover it, decide it is worth indexing, and then learn what it is about. Those are three separate jobs and they happen in that order.
Most founders skip straight to keywords. They buy a tool, build a list of terms, and start writing. Then nothing happens for months and they assume SEO is broken. What is usually broken is discovery. Google literally does not know the site exists yet.
We launch new sites often, and the first two weeks after launch are almost entirely technical. Content comes after the plumbing works.
It means making your site easy to find, easy to read, and easy to trust. Nothing about a new site is special to Google. It gets no head start and no penalty. It simply has no data attached to it yet, so every signal you create carries more weight than it will later.
Google is blunt about how discovery works. Its documentation on how Search works states that "there isn't a central registry of all web pages, so Google must constantly look for new and updated pages and add them to its list of known pages." Nobody tells Google you launched. You have to leave a trail.
Google is equally blunt about the limits. The same documentation says "Google doesn't guarantee that it will crawl, index, or serve your page, even if your page follows the Google Search Essentials." A new site is not entitled to a spot. It has to earn one.
That sounds discouraging. In practice it is freeing, because it means the work is concrete. Get crawled. Get indexed. Give each page a clear job. Everything else is refinement.
Longer than you want and shorter than the internet claims. Indexing can happen within days. Meaningful rankings for anything competitive usually take months. Google's own SEO Starter Guide says "some changes might take effect in a few hours, others could take several months" and suggests waiting a few weeks before judging a change.
The gap between indexed and ranking is where most new site owners give up. Your pages are in the index within a week, you search your brand name and find yourself, and then you search your actual service and find nothing. That is normal. Being in the index is table stakes, not success.
We tell clients to plan on a first useful signal within roughly one quarter and real traction across two or three. That is not a promise, it is a planning assumption. Anyone selling faster than that on competitive terms is either lucky or lying.
The one thing that genuinely speeds this up is picking easier targets first, which we come back to below.
Submit a sitemap in Google Search Console, then use the URL Inspection tool to request indexing on your most important pages. Make sure your robots.txt is not blocking anything and that no page carries a stray noindex tag from the staging build. Then get one or two real links pointing at the domain.
The staging noindex is the single most common launch bug we find. A site is built behind a password with noindex applied site wide, it goes live, and nobody removes the tag. The site is perfect and completely invisible. Check this on launch day and check it again a week later.
Google Search Console is not optional. It is the only place you get to see what Google actually thinks of your site rather than what a third-party tool guesses. Verify the property before launch so you have data from day one. We walk through the whole tool in our guide to using Google Search Console.
Links matter here in a narrow, practical way. You do not need a link campaign. You need a couple of places where your domain appears so crawlers have a path in. A real business listing, a partner site, a directory in your industry. Google's sitemap documentation even names your situation directly, listing "your site is new and has few external links to it" as a reason to submit a sitemap.
Probably yes, even though Google says small sites often do not. Google defines small as "about 500 pages or fewer" and says a comprehensively linked site may not need one. But a brand new site has no external links feeding crawlers in, and that is exactly the case Google says a sitemap helps with.
The cost is close to zero. Webflow generates a sitemap automatically, and most modern stacks do the same. The only work is confirming it exists, confirming it lists the pages you want indexed, and submitting it once in Search Console.
Size will not be your problem. Google states that "all formats limit a single sitemap to 50MB (uncompressed) or 50,000 URLs." A new business site is nowhere near either limit, so a single file is fine and splitting is a problem for later. We go deeper on the format itself in our XML sitemap guide.
What does matter is accuracy. A sitemap listing pages that redirect, 404, or carry a noindex tag sends mixed signals on a site that has no other signals to fall back on. Clean it before you submit it.
Fix speed, structure, and titles. A new site gets judged on the pages it already has. If those load slowly, use vague titles, and bury the main content behind JavaScript, no amount of blogging will rescue them. The foundation is cheaper to get right at launch than to retrofit later.
Speed has published targets, so there is nothing to guess about. Google's web.dev documentation sets the good thresholds at 2.5 seconds for Largest Contentful Paint, 200 milliseconds for Interaction to Next Paint, and 0.1 for Cumulative Layout Shift, measured at the 75th percentile of page loads across mobile and desktop. Hit those and speed stops being a liability.
Structure means one clear H1 per page, question shaped H2s where it fits, and real text in the HTML rather than text painted in by script after load. Google lists JavaScript rendering issues among the common reasons pages fail to get indexed, and AI answer engines are less patient than Google is.
Titles are the cheapest win on a new site. Every page needs a title tag that says what the page is, with the words a real person would search. Generic titles like "Home" and "Services" waste the strongest on-page signal you have.
Fewer than you think, but each one finished. A tight site of eight to twelve strong pages outperforms a sprawling site of forty thin ones. Google names low content quality as a common barrier to indexing, and thin pages on a new domain are the fastest way to trigger it.
Our usual launch shape is a home page, a services or product page for each thing you actually sell, an about page, a contact page, and two or three proof pages such as case studies. That is enough to explain the business and enough for Google to build a picture of what the site is for.
Resist the urge to publish thirty blog posts at launch. A new domain publishing a large batch of shallow content looks exactly like the thing Google's spam systems are built to catch. Steady beats sudden. We publish daily on this blog, but we did not start there on day one of the domain.
Each page should have one job and say so in the first screen. If you cannot describe a page's job in one sentence, it is not ready to publish.
Small ones, without hesitation. A new domain will not outrank an established competitor on a two word head term. It can absolutely win a specific five word question that nobody has answered properly. Those wins compound, and they teach Google what your site is about.
Specific queries also match how people search now. When someone asks ChatGPT or Perplexity a real question, the answer gets assembled from pages that address that exact question directly. Broad pages get skipped in favour of precise ones.
The trap is picking easy keywords that nobody with money ever types. Easy and worthless is still worthless. We look for queries that are specific enough to win and close enough to a buying decision to matter, which usually means comparison and how-to questions inside a narrow niche. Matching the format to the goal behind the query is the whole game, and we break that down in our piece on search intent and how to match it.
Pick one narrow topic and cover it properly before moving to the next. Depth in one area builds recognisable expertise faster than one post each across ten areas.
Measuring the wrong thing too early. New site owners watch rankings daily, panic at movement that means nothing, and change strategy every three weeks. SEO on a new domain is slow and noisy at the start. Constant changes make it impossible to learn what worked.
The second mistake is treating SEO as a phase. A site is not optimised once and then done. Every new page either strengthens the picture Google has of your site or muddies it. That is why we care about internal linking and consistent terminology from the first ten pages, not the first hundred.
The third is copying a competitor's structure without understanding why it exists. A competitor with a decade of authority can rank a thin page on brand strength alone. You cannot. Copy their thinking, not their output.
Google is honest that indexing itself is conditional, stating plainly that "indexing isn't guaranteed; not every page that Google processes will be indexed." Read that as permission to focus. Publish fewer pages that deserve to exist.
Do four things this week. Verify Google Search Console and submit your sitemap. Check every page for a leftover noindex tag. Run your key pages against the Core Web Vitals thresholds. Then rewrite your title tags so each one names what the page is and who it is for. That is the whole first sprint.
After that, pick one narrow topic and write the best page on the internet about it. Then do it again. Everything else in SEO is a refinement of those two habits.
If you are launching something and want the technical foundation handled properly before you start writing, we are happy to walk through it with you. Getting this right at launch is far cheaper than fixing it in a year. Reach out through phoenix.studio and tell us what you are building.
Tell us where you want to go. We'll tell you how we'd get you there.