Answers to read before you hire.

A builder is the right answer for some businesses and the wrong one for others. Here is how to tell which you are, and what to check before you commit either way.

Each kind of provider suits a different project. Here is a framework built on scope, continuity and who actually does the work, plus an honest note on the limits of a one-person studio.

Prices are easy to compare and hard to judge. This is a checklist of the things that actually separate a good engagement from a bad one, with the warning signs worth walking away from.

Screenshots show what someone can make look good. Live sites show whether it works. This is a short test you can run on any portfolio in about half an hour, including mine.

A marketplace listing and your own website do different jobs. This is a plain framework for deciding what each should do for your business, and when the website matters more.

Neither is better in general. The real question is who will change the pages, how often, and who will keep the software up to date. This note sets out the trade-offs honestly.

Distance changes how a project is run, not how it is judged. Agree how you will talk, share access with roles instead of passwords, and keep the scope in writing.

Two promises sit behind almost every website quote: it works on a phone, and it works for people with different abilities. Here is how to check both without being an expert.

Many businesses ask for an online store when they need a catalogue that brings in enquiries. The difference is who completes the sale, and it changes the cost, the risk and the provider you need.

Both endings work. The choice depends on who your customers are and whether you may sell abroad. This note sets out what Google says, a simple decision table and the ownership steps that matter more than the ending.

A backend is not a sign of a better website. It is extra machinery that stores data and runs rules. Here is when a business site needs one and when it does not.

Late and scattered feedback is a common reason projects drag. A few habits keep revision rounds short and the schedule intact. They apply to any developer.

A catalogue site succeeds when a buyer can ask for a quote in a minute and you receive what you need to answer it. This note covers the fields, the routes and the follow-up.

Calendar time depends less on how fast anyone types and more on content, approvals and access. Here is what moves a schedule, and how to plan one that holds.

A catalogue works when a buyer can get from a need to the right product in a few clicks. This is a practical structure, with a worked example and honest limits for sites without a search engine of their own.

Photographs are usually the heaviest thing on a business page. Sizing them for the screen, reserving their space and describing them well makes a site faster and easier to use.

A single page suits one clear offer. Most businesses with several services or products need separate pages, because each page is an address a visitor can land on and share.

Most search losses after a redesign come from changed addresses and missing redirects. This is the order of work that Google's own site-move guidance recommends, in plain language.

A one-page brief gets you a better quote and fewer misunderstandings. Copy the template, fill in what you know, and write "not sure" where you are not.

A walk through a website project in order, so you know what happens, what is asked of you, and which items need to be written into the agreement to be included.

A page earns its place by answering a question a visitor really has. Here is the core set, the pages that depend on your business, and a test for pages you can leave out.

Missing material, rather than design or code, is a common reason a website is held up. Gather these items first and the project can move at the speed of the build.

Two packages can both say "SEO included" and mean completely different things. Here is a checklist for putting them side by side, using Google's own guidance on what is and is not possible.

Two quotes with different totals are rarely quotes for the same thing. These are the lines to compare, the questions to ask when a line is missing, and how to spot a low price that leaves things out.

A fixed budget does not buy a fixed website. It buys a scope. Here is how to spend ₹30,000 on a business website without the surprises that appear after the quote is signed.

There is no single price for a website, and published price guides disagree widely. Here is what actually moves the cost, and the recurring costs people forget.

A click on a call or WhatsApp button is a sign of interest, not a customer. This note shows a simple enquiry log, what GA4 can add, and what you must never send to an analytics tool.

GA4 counts things that happen on your site and calls them events. Understanding what an event is, and what it cannot tell you, is most of what a business owner needs.

A report can look impressive and tell you nothing. Learn which numbers come from Google, which are estimates, and what questions to ask when the report shows activity but not results.

Local search and nationwide search work on different signals. Know which one your business needs, whether you are eligible for a Google Business Profile, and why a page for every city does not help.

Two free Google tools answer two different questions. Here is what each one shows, what counts as an enquiry, why a tap is not a sale, and what to decide about privacy first.

A big site is not a better site. This note explains when extra pages help, when they hurt, and a simple test for whether a page deserves to exist.

A new site shows little in Search Console for a while, and that is expected. This note says what to set up, what to look at each week, and which numbers to leave alone.

People type similar words for very different reasons. A page that answers the wrong reason will not help, however well it is written. This is how to read intent and match it.

Search work is mostly a set of sound basics, patience and honest content. Here is what is within your control, what is not, and which promises to treat as warning signs.

A sitemap lists the pages you want found. A canonical address says which version of a page is the main one. Neither guarantees anything, but mistakes in either can cause real problems.

Search engines and readers use the same few signals to understand a page. This checklist shows what to write for each, with examples of weak and clear versions.

Most missing sites are brand new, blocked by a setting, or not yet found. Work through these checks in order before you pay anyone to fix it.

When a website disappears, the cause is usually one of three accounts. Knowing which does what turns a panic into a phone call to the right company.

Hosting offers range from free to expensive, and the label tells you little. These are the questions that show what you are really getting and who is responsible for what.

No hosting choice is safe against everything. Here is what the padlock covers, where real risks usually sit for each kind of site, and a short routine for backups and accounts.

Speed is not one number. Here are the three measures Google publishes, what usually makes a business site slow on a phone, and what a good score does and does not buy you.

Launch day is when most owners find out what they did not ask for. This is a checklist of what to hold at the end, so that the site is yours to run, change or move.

Launch day is when small mistakes become public. Work through this checklist with your developer before the site goes live, on launch day and in the first week.

A website has several separate accounts, and each is a door. Keep a list, give people only the access they need, turn on two-step verification and remove access when a project ends.

Visitors who leave without calling are telling you something. Check whether they are the right people, whether the next step is obvious on a phone, and whether the page answers the question they came with.

A maintenance plan is only worth paying for if you can say what is checked, how often, and what is left out. Here is how to read one, and when to decline.

Owners usually discover who holds the domain only when something goes wrong. Here are the four things to settle in writing first, and how to check the one you can verify yourself.