Technical SEO has a reputation for being intimidating, but for a new website the essentials are surprisingly manageable. The goal is simple: make sure search engines can find your pages, understand them, store them in the index and serve them to the right searches — without technical obstacles getting in the way.

Getting these basics right at launch is dramatically cheaper than repairing them later, when structure changes require redirects and re-indexing. Here is what matters, in priority order.

1. Make your site crawlable

Search engines discover content by following links. Your job is to make that journey easy:

  • Every important page should be reachable by clicking links from somewhere else on the site — no orphan pages.
  • Use clean HTML links. Content that only appears after complex JavaScript interaction should be used carefully; if Google cannot see it reliably, it cannot rank it.
  • Create a logical structure: homepage → category/service pages → detail pages, ideally within three or four clicks of the homepage.

2. Tell Google what to crawl: robots.txt

The robots.txt file sits at yoursite.com/robots.txt and instructs crawlers which areas to skip. Keep it simple and permissive for content you want ranked. Common uses: blocking admin folders, staging environments or search-result pages that create duplicate URLs. A single wrong line (like blocking the whole site) can remove a website from search — check it after any platform migration.

3. Submit a sitemap

An XML sitemap lists the pages you want indexed. Keep it accurate: only canonical, indexable, valuable pages. Submit it in Google Search Console and monitor the Page indexing report — it tells you which URLs were discovered, indexed or excluded and why. Search Console is free and it is the single most important diagnostic tool in technical SEO.

4. Solve duplicate content with canonical URLs

Most duplicate content is accidental: www vs non-www, http vs https, trailing slashes, parameter-based URLs and paginated pages all create near-copies. Left alone, they split ranking signals across versions. The fixes are standard:

  • Choose one canonical hostname and protocol, and redirect the rest (e.g. everything to https://www).
  • Use rel="canonical" tags to name the preferred version of a page.
  • Avoid publishing the same article at multiple URLs; use redirects when URLs must change.

5. Be mobile-first

Google predominantly uses the mobile version of your pages for indexing and ranking. Test your site on a real phone: readable text without zooming, tap targets that are comfortable, no horizontal scrolling, and content identical to the desktop version. A responsive layout is the modern default and removes the need for separate mobile URLs.

6. Care about page speed — proportionally

Speed is a ranking factor and, more importantly, a user experience factor. For a typical small business site, the biggest wins are boring and effective:

  • Compress and correctly size images (usually the #1 problem).
  • Minify CSS/JavaScript and remove unused libraries.
  • Use caching and a CDN where practical.
  • Lazy-load below-the-fold images.

Measure with PageSpeed Insights and Core Web Vitals (LCP, INP, CLS), then optimize the slowest, most important pages first. Do not chase perfect scores on pages no one visits.

7. Add structured data

Structured data (schema.org markup in JSON-LD) describes your content to machines: this is a local business, this is a service with a price range, this is an article with an author. It powers rich results and helps search engines classify your pages. Keep it truthful — markup that misrepresents the page can trigger penalties. Common useful types: Organization, LocalBusiness, Service, Article, FAQPage and BreadcrumbList.

8. HTTPS and basic health

Serve everything over HTTPS with a valid certificate — browsers now label plain HTTP as "not secure", which damages trust and conversions. Alongside HTTPS, check for broken links (404s), soft-404 pages (empty pages returning "success") and redirect chains, all of which waste crawl budget and frustrate users.

A launch-day technical checklist

  1. HTTPS live on all URLs, no mixed-content warnings
  2. robots.txt present and not blocking anything important
  3. XML sitemap generated and submitted to Search Console
  4. Google Analytics (or an alternative) installed
  5. One H1 and unique title/meta description per page
  6. Canonical tags in place
  7. Mobile layout verified on a real device
  8. Test in PageSpeed Insights; fix anything obviously heavy
  9. Structured data added for organization/service types
  10. Checked from the outside: site:(yourdomain) search shows your pages

None of this requires a huge budget — it requires doing it deliberately, once, at the start. If your website missed some of these steps, a technical SEO audit will pinpoint exactly what to fix, and the SEO packages cover the remediation work. Questions about a specific issue? Send me the URL — I look at new websites all the time.

Frequently asked questions

How do I know if my site has technical SEO problems?

Start with Google Search Console's Pages and Core Web Vitals reports — they show indexing and experience issues in Google's own words. A professional technical SEO audit then prioritizes fixes by impact.

Can technical SEO be fixed without rebuilding the website?

In most cases, yes: redirects, metadata, sitemaps, robots.txt, image compression and many speed fixes apply to existing sites. A rebuild is only worth it when the platform itself fights optimization — compare both paths in HTML vs WordPress.

How often should technical SEO be checked?

A full audit yearly (or after redesigns and migrations), with Search Console reviewed monthly. New errors appear silently — monitoring beats rescue missions.

Continue reading

Go deeper: how website speed affects SEO and the 12 essentials of an SEO-friendly website.

Applied workbook: turn the guidance into a working plan

This section is for a founder or developer preparing a new website for launch. Its purpose is to help you launch with crawlable, indexable and maintainable foundations. It expands the principles above into a planning document you can use with a colleague, freelancer or agency. It is not a promise of a ranking, lead volume or return. Those outcomes depend on the market, offer, website, competition, budget and quality of execution.

Use this Technical SEO Basics for New Websites workbook on one real priority rather than answering it in the abstract. A useful plan names the page, campaign, audience or dataset being discussed; identifies the evidence available today; and gives the next action to a specific owner. If information is missing, write that down as a research task instead of filling the gap with an assumption.

A realistic planning situation

Consider this hypothetical situation: a new site looks complete in a browser but has not yet been checked for canonical URLs, status codes, sitemaps or mobile performance. The example is intentionally general and does not describe a named client. It shows why the topic cannot be solved by copying a template. The right response begins by separating what is known from what merely sounds plausible.

For Technical SEO Basics for New Websites, first describe the commercial objective in one sentence. Then describe what a useful visitor, lead or customer would do next. Finally, identify the present obstacle. It might be missing demand, weak relevance, technical friction, an unclear offer, poor measurement or insufficient follow-up. Each obstacle leads to different work, so this diagnosis prevents a tool from deciding the strategy.

For the Technical SEO Basics for New Websites situation, create two columns: evidence and assumptions. Evidence may include search queries, campaign terms, page behavior, sales notes, crawl output or verified records, depending on the topic. The plan should test the most important assumption while protecting what the available evidence already supports.

Information to collect before implementation

Do not wait for perfect data, but collect enough information to avoid an expensive guess about Technical SEO Basics for New Websites. The following inputs are specific to this topic:

  • 1. the final production domain and preferred URL format. Note its source, date and any limitation before using it to make a decision.
  • 2. a complete route inventory and redirect list. Note its source, date and any limitation before using it to make a decision.
  • 3. robots, sitemap, canonical and structured-data output. Note its source, date and any limitation before using it to make a decision.
  • 4. mobile performance and form testing on production-like hosting. Note its source, date and any limitation before using it to make a decision.

Place the Technical SEO Basics for New Websites inputs in one brief. Add the target market, device or location where it changes the answer. For international work, terminology and competition can differ between the United States, United Kingdom, Canada, Australia, Europe and Bangladesh; that does not justify repeating country names throughout the copy. It means the research should reflect the audience that will actually see the page or campaign.

Finish the Technical SEO Basics for New Websites brief with constraints: budget, deadline, access, approval time, technical capacity and legal or platform requirements. Constraints make priorities visible and help a specialist recommend a focused first phase instead of pretending every possible task belongs in the initial scope.

Four decisions to make deliberately

1. Control indexation

Keep private, duplicate and utility routes out while allowing valuable pages to be crawled. Write down the current evidence before changing anything. Then make one controlled decision and record who owns the next action.

Working note for Control indexation: connect this decision to launch with crawlable, indexable and maintainable foundations. Record the assumption, the evidence available now and the condition that would make you revise this specific choice. That keeps the work practical and prevents a checklist from replacing judgement.

2. Choose canonical URLs

Make internal links, redirects, canonicals and sitemap entries agree. Apply this to the page, campaign or workflow that matters most first. A narrow test is easier to interpret than a site-wide change made without a baseline.

Working note for Choose canonical URLs: connect this decision to launch with crawlable, indexable and maintainable foundations. Record the assumption, the evidence available now and the condition that would make you revise this specific choice. That keeps the work practical and prevents a checklist from replacing judgement.

3. Return honest status codes

Use real 404s and permanent redirects instead of masking missing pages. Explain the choice in plain language to the person approving the work. If the reason cannot be explained clearly, the scope probably needs more research.

Working note for Return honest status codes: connect this decision to launch with crawlable, indexable and maintainable foundations. Record the assumption, the evidence available now and the condition that would make you revise this specific choice. That keeps the work practical and prevents a checklist from replacing judgement.

4. Measure after launch

Verify Search Console ownership, submitted URLs and real-user performance. Set an explicit review point. The first implementation may reveal a different constraint, so the plan should allow evidence to change the next priority.

Working note for Measure after launch: connect this decision to launch with crawlable, indexable and maintainable foundations. Record the assumption, the evidence available now and the condition that would make you revise this specific choice. That keeps the work practical and prevents a checklist from replacing judgement.

How to move from plan to implementation

Turn the four Technical SEO Basics for New Websites decisions into a short backlog. Each item should contain an owner, the asset or account affected, the expected user benefit, the evidence behind it and a completion check. Broad instructions such as “improve it” are not executable; name the exact page, campaign, file or workflow and the check that will close the task.

For the Technical SEO Basics for New Websites plan, work in dependency order. Measurement and access usually come before optimization, and a clear offer or source dataset comes before scaling distribution. The correct sequence reduces rework and makes later evidence easier to interpret.

Keep a dated change log for Technical SEO Basics for New Websites. Record the content, technical, tracking, audience, creative or data rule that changed—whichever applies here. Platforms change continuously, but undocumented internal releases cause just as much confusion. A log separates deliberate work from seasonality and normal fluctuation.

Review the Technical SEO Basics for New Websites implementation as the intended user would. Use the actual device, landing page, account view, spreadsheet or conversion path; then complete the intended task. Technical correctness matters, but the work is unfinished when a real person cannot understand or use it.

Measurement that supports a decision

A reporting dashboard for Technical SEO Basics for New Websites is useful only when each number changes a decision. Start with the following topic-specific measures:

  • valid indexable URLs: define where the number comes from, how often it will be reviewed and what business question it answers. Compare like-for-like periods and annotate major releases or campaign changes.
  • sitemap discovery and index coverage: define where the number comes from, how often it will be reviewed and what business question it answers. Compare like-for-like periods and annotate major releases or campaign changes.
  • redirect and broken-link errors: define where the number comes from, how often it will be reviewed and what business question it answers. Compare like-for-like periods and annotate major releases or campaign changes.
  • Core Web Vitals and conversion-form health: define where the number comes from, how often it will be reviewed and what business question it answers. Compare like-for-like periods and annotate major releases or campaign changes.

For Technical SEO Basics for New Websites, use both leading and outcome indicators. A leading indicator shows whether implementation is moving in the intended direction; an outcome indicator shows whether that direction supports the business. The measures listed above make that distinction concrete, and neither group should be interpreted alone.

Avoid presenting correlation as certainty when reporting on Technical SEO Basics for New Websites. Traffic, cost or conversion can change because of seasonality, competitors, pricing, creative, tracking or demand. Report the release, the observation and the next test instead of claiming credit the data cannot isolate.

Quality-control and risk review

Before calling the Technical SEO Basics for New Websites work complete, check for these topic-specific warning signs:

  • blocking the production site. Treat this as a review trigger, not a reason to abandon the channel. Check the underlying evidence, correct the process and document what changed.
  • shipping staging canonicals. Treat this as a review trigger, not a reason to abandon the channel. Check the underlying evidence, correct the process and document what changed.
  • JavaScript-only essential content. Treat this as a review trigger, not a reason to abandon the channel. Check the underlying evidence, correct the process and document what changed.
  • launching without a redirect map. Treat this as a review trigger, not a reason to abandon the channel. Check the underlying evidence, correct the process and document what changed.

Also run a cross-channel check around Technical SEO Basics for New Websites: links should resolve to the intended URL, important content should be available on mobile, images should have accurate alternative text where needed, forms should explain what happens next, and analytics should not claim more than the implementation supports. These details affect accessibility, trust and measurement together.

Ask someone who was not involved in the SEO implementation to explain the page, campaign or process after a short review. If their understanding differs from the intended message for Technical SEO Basics for New Websites, improve the work before adding more traffic or content. Clarity is often the cheapest useful improvement available.

A 30-day review rhythm

For Technical SEO Basics for New Websites, use this first-month rhythm: Days 1–3: establish the baseline and choose one priority. Days 4–10: complete the first controlled implementation and quality checks. Days 11–20: observe early signals without reacting to every daily movement. Days 21–30: compare the evidence with the original assumption and approve the next iteration.

The exact SEO timing depends on how quickly reliable evidence appears. Technical defects can be verified after release, organic search effects often need longer observation, and paid campaigns still need enough qualified activity to support a decision. Review Technical SEO Basics for New Websites at a pace that matches the system rather than an arbitrary daily reporting habit.

Document the handover

Close the Technical SEO Basics for New Websites cycle with a one-page handover. List the objective, the assets or accounts changed, access ownership, the baseline date, completed checks, unresolved risks and the next review date. Attach the small number of reports or source files another person would need to continue the work. For a founder or developer preparing a new website for launch, this record is especially useful because it turns SEO activity into an understandable operating process instead of knowledge held by one provider. The handover should also state what was not done and why. That boundary prevents later assumptions about scope, makes future quotations easier to compare and protects authentic reporting. If a result has not yet had enough time or data to evaluate, label it as pending rather than positive or negative. Clear documentation is part of delivery, not an optional administrative extra.

Workbook questions

What should I do first?

For Technical SEO Basics for New Websites, start by writing the objective and collecting the four inputs above. Then choose the decision that removes the largest current uncertainty. That is usually more valuable than selecting the easiest task or the tool with the most recommendations.

How do I know whether I need professional help?

Professional support with Technical SEO Basics for New Websites is useful when access, technical implementation, research depth or ongoing management exceeds the time and skills available internally. Ask for a written scope, named deliverables, ownership and reporting method. You should understand the SEO work even when you are not doing it yourself.

Can this process guarantee a result?

No. This Technical SEO Basics for New Websites process improves decision quality and implementation discipline; it cannot control competition, platform auctions, algorithm changes, customer demand or sales follow-up. Be cautious with anyone who guarantees rankings, leads or revenue without those dependencies.

How does Prosengit Kundu approach this work?

For work related to Technical SEO Basics for New Websites, Prosengit Kundu connects the SEO decision with its technical destination where relevant: content, advertising, social or YouTube marketing, B2B research, and custom HTML/CSS/JavaScript or WordPress development. The scope begins with the goal and available evidence. Review the digital marketing and website services, see related case studies, or describe the project.