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: planning website guides and reviewing common project questions
    Reading paths

    Follow the questions in a useful order.

    These sequences connect in-depth articles and practical guides. Follow all three steps or start with the one that addresses your current problem.

    SEO and SXO journeys

    Connect visibility with a website people can use to decide.

    Four routes connect diagnosis, page structure, usability and measurement. Start with the obstacle you can observe, then follow the complementary articles.

    Library

    79 topics to make better decisions

    Ask a question

    How should a JSON article library be versioned?

    Each JSON article needs a stable ID, unique slug, publication date and modification date. The file also needs a schema version and update timestamp.The useful answer…

    How do you optimize a contact form for conversion?

    A useful form collects what serves the first exchange, explains errors and confirms the enquiry’s actual status. Test on a phone and by keyboard through to receipt by…

    Which Schema.org data is useful for a web agency?

    Choose Schema.org data through actually published information: organisation, person, article, service or navigation. Define reference identity and page relationships…

    How do you secure a redesign with minimal SEO loss?

    Treat a redesign as a migration of content, URLs and functions. Inventory what still serves a purpose, assign destinations to old addresses and define acceptance before…

    Why is a dated sitemap essential for a content website?

    A sitemap helps identify URLs you want discovered. A useful lastmod reflects a significant page change rather than every XML generation. Check canonical URLs and dates…

    How do you integrate accessibility into SEO and SXO?

    Accessibility belongs in SEO and SXO work because it improves the ability of different people to understand, navigate and use a page. Its primary purpose is equal access…

    How do you read server logs to prioritize an SEO audit?

    Server logs record what was actually requested from a website. Depending on configuration, they can contain the URL, time, response status, transferred bytes, referrer…

    How do you build a conversion-centered SEO and SXO audit?

    A useful SEO and SXO audit connects every search entry point to an intent, a page experience and a measurable outcome. Its purpose is not to produce the longest possible…

    Should you still publish an RSS feed for social media?

    An RSS feed can supply a reader or distribution tool that supports it. Establish the actual consumer and its behaviour first. The feed carries published articles, links…

    Do images and videos help generative search visibility?

    Images and videos help when they convey information difficult to explain otherwise: a product, action, place or comparison. Provide context, accessible alternatives…

    How do you prepare a PHP website for modern SEO?

    A PHP website does not need an SEO recipe specific to its language. Check HTTP responses, URLs, generated HTML, links, intended indexing and useful journeys. Server…

    How do you build a 90-day AI SEO roadmap?

    A 90-day roadmap should produce decisions, fixes and interpretable observations. Choose priority pages and tasks, then distinguish delivered work from measured effects…

    How do you organize article production with GPT-5.6?

    Organise model-assisted production around a brief, approved sources, review and a publication decision. GPT-5.6 identifies the tool discussed here without fixing its…

    How do you use Search Console after an editorial reset?

    After editorial changes, compare retained, moved and retired pages with their previous state. Check access, redirects, canonicals and internal links first, then examine…

    Why does user experience influence search visibility?

    User experience first affects understanding and task completion. Some technical aspects also matter to search, without guaranteeing rankings. Measure a concrete obstacle…

    How do you document E-E-A-T and proof on a website?

    Trust is documented through facts: who writes or contributes, which sources support the work, what expertise is relevant and within what scope. A case study should…

    How do you prioritize a technical SEO audit in 2026?

    Prioritise a technical audit by observed obstacles and consequences: content access, intended indexing, blocked tasks and inconsistent information. Link each finding to…

    How do you build local content that helps AI and SEO?

    Useful local content explains what actually changes with location. Use approved contact details, a dated geographic source and real business conditions. A town name or…

    How do you improve LCP and CLS on a showcase website?

    LCP and CLS address different difficulties: main-content appearance and layout stability. Reproduce loading under known conditions, identify the affected element and fix…

    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