Publish the website setup before you publish the articles. A business site needs one address that search engines should index, a title and description on each public page, a sitemap, and a page that states the company name, the city, and how to make contact. Articles do not repair a site that is missing those.
This is the setup used on AppClust's own site, written so a service business in the UAE or India can copy the checklist. It does not claim a ranking, a traffic number, or a price. Current plan names are on the SEO growth plan. The figures, if you need them, stay on the pricing page.
One host, and one canonical URL
Pick the host you want indexed and send every other host there. On this site, requests to appclust.com redirect to https://www.appclust.com. Each blog post then sets its own canonical to its own address under /blogs/. A location page that repeats another page should not compete with it. The Dubai page is https://www.appclust.com/website-development/dubai, and that URL is its own canonical. The old UAE path redirects there. Link the Dubai page when you mean the Dubai office. Do not build a campaign around a duplicate city URL.
Country-swap routes, including India, canonical to /website-development and are marked noindex. Do not use them as internal links. If a country page has no unique address, phone, or client proof, indexing a swapped copy of the same page splits attention across URLs that say the same thing.
Titles and descriptions you would actually read
One visible H1 per page. The title tag can match it, and it should stay under about 60 characters so it is less likely to be cut in a search result. The meta description should stay under about 160 characters and finish a sentence. On this blog, a stored seo title is used as the full title tag, so the brand suffix is not added a second time. A missing description is sliced from the excerpt at 160 characters, which can end mid-word. Write the description on purpose.
Put the primary phrase in the H1 and once in the first paragraph. Do not paste it into every heading. A page about website migration should say migration. A page about a clinic's services should say the services. Keyword lists in the title are how a useful page starts to look like a directory.
The pages that have to exist
A service business usually needs a home page, a clear services page, proof, a way to enquire, and a pricing or scope page if you sell a defined offer. AppClust publishes those as website development, solutions, case studies, contact, and pricing. A blog is the next layer, after those pages answer who you help and what you sell.
Name the company and the place on a page a person can open. This site states Erratum Solutions FZCO, Dubai Silicon Oasis, the phone +971 55 768 6294, and info@appclust.com. The same facts are in the LocalBusiness schema for the Dubai office. If the footer, the contact page, and the schema disagree, fix the pages before you add more markup.
Sitemap, robots, and what stays out
robots.txt on this site allows / and disallows /api/, /admin/, and /invoice/. It points at https://www.appclust.com/sitemap.xml. The sitemap lists the public marketing pages, the solution pages, the case studies, every blog post, and the Dubai page. It does not list the invoice app or the noindex country-swap URLs.
A private tool, a draft, and a query-string report should not be in the sitemap. The website analyzer adds a noindex header when the URL includes a ?url= scan. That is the right pattern for a tool that generates a new page per input.
What to publish after the setup
Write articles that point at a service page with a specific anchor. A post about technical SEO should link to the Next.js migration page and to the technical SEO note. A post about moving an old site should link to the migration checklist. A comparison of stacks should link to Next.js and WordPress. Those links are how a cluster works. A blog that only links to other blog posts never reaches an enquiry.
Starter includes basic SEO setup. Professional includes SEO and blogs setup. Enterprise includes advanced SEO. That is the split named on the SEO growth plan. This article does not restate a price, because the website pages and the pricing file do not currently agree, and a blog should not pick a winner.
A page list you can hand to a writer
A service business does not need a fifty-page site to start. It needs a list someone can finish. A practical first set is: home, about, one page per core service, one proof page or a case-study index, contact, and a pricing or scope page if the offer is packaged. Add a blog only after those pages say who the work is for. Eight to twelve pages is enough for a clinic, a cleaning company, a dealer, or a training center. More pages are justified when each one has a different job, not when a keyword tool produced a city name.
For each page, write one sentence that a stranger could repeat: what this page is for, and what the reader should do next. If two pages share that sentence, merge them or canonical one to the other. The Dubai page has its own sentence, the office in Dubai Silicon Oasis, and its own canonical. A city URL that only swaps the name should not.
How an article earns its place
An article earns a URL when it answers a question a buyer asks before they enquire, and when it links to the service page that can take the next step. 'What should be true before we publish a blog' is that kind of question. 'Top trends in digital transformation' is not, unless it names a job, a person, and a decision. The November 2026 note on the 2027 forecast keeps that test and records what the page will not claim.
Inside the article, use one product link with the words a person would say. 'SEO growth plan' is an anchor. 'Click here' is not. Add the pillar or the sibling when it exists. This page links to the technical note, the migration checklist, and the Next.js comparison because those are the next decisions, not because a tool asked for three links.
Mistakes already visible in thin posts
A short post with no headings, a promise in the title, and a price that does not match the pricing page will not be repaired by publishing another short post beside it. Several older notes on this blog are in that state. They stay up until they are rewritten or, after a Search Console export, redirected. New articles should not copy their FAQ blocks, their percentages, or their prices. If a sentence needs a number you cannot point at in the pricing source or in a primary document, delete the sentence.
What to look at after 30 days
Thirty days after launch, look at Search Console for the pages you meant to index. Confirm the canonical host is the one receiving impressions. Confirm a city URL you canonicalized is not the one collecting clicks. Confirm new articles show impressions for the question they answer, or for nothing yet. Nothing yet is normal. Impressions on the wrong URL are the problem to fix.
Do not add three more articles because the first one is quiet. Add the next article when the service page it should support is the one you want enquiries to reach. The technical SEO note is the file-level version of the canonical and sitemap rules. Use it when a developer is in the repo. Use this page when you are deciding what to publish at all.
A launch checklist
Use this before the first article, and again when a new service page goes live. One canonical host. Apex and any old host redirect to it. Each indexable page has one H1, a title, and a description. Duplicate country pages canonical to the page you want indexed, or they are noindex. The sitemap lists only public URLs. robots.txt points at that sitemap and blocks tools and admin. The contact page, the footer, and the schema share one name, one city, and one phone. The first articles link to a service page. You can check a URL with the website analyzer or the SEO analyzer before you ask for a consultation. Those tools do not replace the setup on the plan.
If you want that checklist applied to a site you already have, book a demo and bring the current URL. You should leave knowing which host is canonical and which pages are allowed to be indexed.





