Search
Enter at least two characters without personal information.

    LibraryArticles & FAQ Your projectRequest a quote
    LanguageEN
    Articles and frequently asked questions

    Simple answers for a better website.

    A library of practical advice to frame a project, avoid common mistakes and make better decisions.

    Creation, redesign, SEO, content, performance or maintenance: each article answers one precise question with explanations you can put into practice.

    • 79topics available
    • Clearanswers without jargon
    • Usefula practical next step
    Illustration: reviewing source documents for practical website guidance
    Library

    79 topics to make better decisions

    Ask a question

    What is an entity strategy for a web agency website?

    An entity strategy clarifies what a site describes and the relationships among organisation, people, services, places and content. Begin with approved facts and a…

    How do you audit a website after a Google core update?

    After a core update, establish the affected period and pages before rewriting the site. Compare suitable queries, devices and periods, then check concurrent migrations…

    Is llms.txt useful for Google and AI assistants?

    An llms.txt file replaces neither robots.txt, a sitemap nor the pages themselves. Before publishing one, identify the documented consumer, intended use and maintenance…

    How do AI Overviews and AI Mode change SEO in 2026?

    AI Overviews and AI Mode add answers and supporting links to Google Search. Website work still centres on accessible, useful and verifiable pages. Separate three…

    What should happen when on-site search finds no results?

    An empty result should explain the search and offer a useful next step: correct a word, remove a filter or open a related topic. Retain the query and visible criteria…

    Should you publish an HTML page alongside a PDF?

    Publish decision-critical information in a directly readable HTML page: steps, conditions, validity date and contact. When a document accompanies it on another project…

    How do you write a useful web form error message?

    A useful error message identifies the field, explains the problem and gives a correction. It stays visible, is associated with the field and makes sense without colour…

    What should an out-of-stock product page show?

    An out-of-stock page should explain unavailability near the purchase action and distinguish a temporary shortage from a discontinued item. Retain useful details and…

    Does every product variant need its own page?

    A variant merits a separate page when it answers a distinct need and has its own useful information. When only a simple attribute changes, one page with a clear selector…

    What should you check in a website project quote?

    Compare a quote by actual scope: pages and content, media, functions, migration, approvals, acceptance checks, access and support. Clarify exclusions, third-party…

    How should quarterly content reviews be organised?

    Start a content review with changeable facts: prices, dates, contacts, rules, tools and conditions. Assign an owner and correct other pages reusing those facts. A…

    How do you detect and repair broken links in articles?

    To repair a broken link, identify the resource and the question it supported. Correct a moved destination, choose an equivalent source for a removed resource, or remove…

    Does an author page improve trust in content?

    An author page is not a ranking shortcut. It helps readers and systems understand responsibility, experience and role when the information is real and consistent.The…

    How do you build a web watch from primary sources?

    A useful watch prioritises vendors, authorities, standards bodies and official projects. Secondary media may reveal a topic, but the card should link to the source that…

    Compare the site’s technical condition with the main visitor task. Targeted work can suffice when administration and dependencies remain maintainable; a rebuild becomes relevant when they block necessary changes. Identify observed obstacles and content worth retaining, then compare scope, full cost and migration risks. A visual preference alone is not enough to decide that an otherwise usable site needs replacement.

    Yes. An initial site can focus on the business, services, useful conditions and reliable contact. Prepare accurate information, publishable photographs and the person who will handle enquiries. The scope then identifies pages, writing, integrations, administration and upkeep. Add a feature when it supports a real visitor task and the team can operate it after launch.

    Yes, projects can be organised remotely, including international work. Agree contacts, working language, review stages and responsibilities before starting. Confirm any travel, photography or on-site work separately. Language versions also need someone able to validate their content; translating a location page does not establish a local office or demonstrate completed work in that place.

    Yes, after reviewing its technology, access arrangements and dependencies. Prepare the domain, hosting, administration tool, providers, backups and important functions without submitting secrets through a public form. The takeover defines what stays, changes or is replaced, then checks forms, email, certificates and restoration. Confirm responsibility transfers and usable access before retiring an existing service.

    Start with pages answering real audience needs: the offer, scope, evidence and next action. Check access, internal links, titles, mobile use and any indexing obstacles. Measure relevant queries and enquiries while retaining data limitations. Better visibility guarantees neither a ranking nor a citation in a generated answer; it should support a useful outcome for the site’s visitors.

    Local content helps when it explains actual coverage, access, travel constraints or service arrangements for that place. Merely replacing a town name adds little value. Start with locations you can document and keep current. Separate an establishment address, a service area and an illustrative project scenario; none should be invented to fill a page.

    No. A configured existing platform can be suitable; custom development should address a business rule, journey or integration that warrants it. Also compare administration, security, dependencies, data portability and ongoing cost. The scope should explain selected functions and limitations. The ability to hand over the site and access matters alongside the initial launch.

    Work proceeds through scoping, content preparation, design, implementation, checks and launch. Each stage identifies who supplies information, who approves it and what acceptance means. Tests cover real journeys, especially mobile use and failure states. Handover covers administration, access, dependencies, backups and agreed ongoing responsibilities.

    Yes, under an agreed support scope. This can cover updates, backups, monitoring and fixes, with response arrangements and exclusions specified. Backups need restoration checks, and key journeys should be repeated after changes. Technical maintenance does not replace the content owner’s approval of prices, hours or claims. Define incident contacts and future handover arrangements too.

    Yes. Share the site address, activity, main difficulty, timing and known constraints. A concrete example helps: a missing enquiry, contradictory information or a journey failing on a phone. The initial discussion identifies useful checks and a possible scope. It cannot establish every dependency remotely or price a takeover without examination.
    Another question?

    Explain the context, even in a few lines.

    Write to us