Technical SEO for Web Applications: A Launch Checklist

Content and reputation decide how high you rank. Technical foundations decide whether you can rank at all. A beautiful site that search engines cannot render, crawl or understand will lose to a plainer competitor that gets the basics right. This checklist covers the foundations to put in place before launch, and what to watch afterwards.

Rendering: make pages readable without waiting for JavaScript

Search engines can execute JavaScript, but rendering is slower and less reliable than reading HTML. Pages that build their content entirely in the browser risk being indexed late, or indexed empty.

For anything you want found, serve the content in the initial HTML. Frameworks such as Next.js make this straightforward: generate marketing pages and articles statically at build time, and render dynamic pages on the server. Keep client-side rendering for private dashboards and interactive tools that should not appear in search anyway.

URLs and structure

• Use short, readable URLs that describe the page: /services/mobile-app-development, not /page?id=482.
• Keep a shallow structure so important pages are a few clicks from the home page.
• Link between related pages with descriptive anchor text. Internal links tell search engines which pages matter and how topics relate.
• Pick one version of each URL, with or without a trailing slash, with or without www, and redirect the others to it.

Metadata on every page

Each indexable page needs a unique title and meta description. Titles of around 50 to 60 characters usually display in full. Descriptions should summarise the page in a sentence or two that makes someone want to click.

Add a canonical tag to every page. It tells search engines which URL is the original when the same content is reachable at several addresses, for example through tracking parameters. Add Open Graph tags too, so links shared on LinkedIn, WhatsApp and elsewhere show a proper title, description and image.

Crawl control

• robots.txt tells crawlers which areas to skip. Use it to keep crawlers out of admin areas and endless filter combinations, but never to hide pages you want removed from search. For that, use a noindex directive.
• An XML sitemap lists the pages you want indexed, with the date each last changed. Generate it automatically so it never goes stale, and submit it in Google Search Console and Bing Webmaster Tools.
• Private areas such as customer dashboards should require sign-in and carry noindex, so they never appear in results.

Structured data

Structured data describes your content in a vocabulary search engines understand, using schema.org types in JSON-LD format. It helps search engines connect your pages to your organisation and can make listings richer.

Useful types for a business site include Organization for your company details, BreadcrumbList for page hierarchy, Article or BlogPosting for articles, Product for things you sell and FAQPage for question-and-answer content. Mark up only what is visible on the page, and validate it with Google's Rich Results Test before launch.

Core Web Vitals

Google measures real-world page experience through three Core Web Vitals, assessed at the 75th percentile of visits:

INP replaced First Input Delay as a Core Web Vital in March 2024, so older audits may not cover it. The fixes are well known: serve optimised images in modern formats with explicit sizes, load fonts without blocking text, keep JavaScript bundles small, and reserve space for anything that loads late. Speed also affects conversion directly, which makes this work pay twice.

Images and media

Images are often the heaviest part of a page and one of the easiest wins. Serve them in modern formats such as AVIF or WebP, at sizes matched to the screen, with explicit width and height so the layout does not jump. Load images below the fold lazily, and load the main hero image eagerly so it counts towards a fast Largest Contentful Paint.

Give each meaningful image descriptive alt text. It helps visitors using screen readers first, and it helps search engines understand the image. Decorative images should have empty alt text so assistive technology skips them.

Bilingual and international sites

If you publish in more than one language, for example English and Arabic for the Gulf, give each language its own URL, such as /en/ and /ar/. Link the versions to each other with hreflang tags so search engines show each visitor the right one.

Arabic pages need right-to-left layout, not only translated text. Mirror the layout, check that numbers and mixed-direction text display correctly, and translate metadata as well as body copy. Machine translation without review tends to rank poorly and read worse.

Migrating without losing traffic

Replacing an existing site is where most search traffic gets lost. Protect it with a redirect map.

1. Export every URL from the old site, including those that attract traffic or backlinks.
2. Map each one to its closest equivalent on the new site.
3. Implement permanent (301) redirects for every mapping, and test them before launch.
4. Carry over titles, descriptions and structured data for pages that keep their purpose.
5. Submit the new sitemap on launch day and watch Search Console for crawl errors in the weeks after.

Rankings often fluctuate for a few weeks after a migration. With a complete redirect map, they usually settle at or above their previous level.

After launch

Verify the site in Google Search Console and Bing Webmaster Tools, submit the sitemap, and check the indexing and Core Web Vitals reports every month. Watch for pages excluded from the index, redirect chains and slow templates.

Some sites now also publish an llms.txt file, a plain-text summary written for AI assistants. It is an emerging convention rather than a standard, but it costs little to add and gives AI tools an accurate description of your business.

We build web applications with technical SEO designed in from the first commit: server rendering, structured data, fast pages and clean migrations. If you are planning a new site or a rebuild, tell us about it, or read our guide to choosing a development partner first.