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…
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.
- 109topics available
- Clearanswers without jargon
- Usefula practical next step
Library
Ask a question109 topics to make better decisions
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…
How should redirects be handled when an article title changes?
A title change does not always require a new slug. Keep an accurate old URL; when it becomes misleading, redirect it directly to the new canonical address. The useful…
Why should tracking parameters be removed from editorial links?
UTM parameters help controlled campaigns but rarely belong in citations to official documentation. They lengthen URLs, reveal tools and create variants. The useful…
How do you verify that an RSS feed is valid and discoverable?
An .xml URL does not prove a feed works. Check HTTP status, MIME type, encoding, channel structure and items, then advertise it with link rel="alternate". The useful…
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…
Should a news item be updated or published as a new article?
Update when topic, intent and URL remain the same. Publish a new entry when the event has its own date, consequence or distinct angle. The useful answer depends on the…
How can a site support web agents without exposing sensitive actions?
Agent-friendly structure does not mean unlimited access. Public content can be clear while actions remain protected by authentication, authorisation, confirmation and…
How can articles be published without depending on a generation API?
A public site does not need an AI call when a reader opens an article. Content can be drafted, reviewed and stored in versioned JSON, leaving the site predictable and…
How do you choose between GPT-5.6 Sol, Terra and Luna for content production?
The best model is not automatically the strongest. Sol fits complex briefs and difficult decisions, Terra balances quality and cost for daily work, and Luna suits fast…
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…
How can an editorial RSS feed work without AI generation?
A useful RSS feed needs no request-time generation. Title, first paragraph, canonical URL, category and date are enough, removing cost, latency and API failure. The…
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.