Technical 01
Noindex and robots.txt: decide what stays accessible and indexable
Preventing crawling and requesting exclusion from results are different decisions. First decide whether a page should remain available to readers.
GUIDES / 2026
Technical · SEO
Concrete methods for deciding, building, publishing and measuring. Every guide includes a worked example, an infographic and an actionable checklist.
23 guides
Technical 02
WordPress crawler tracking: read logs before choosing a plugin
The historical post introduced a crawl-tracking plugin. A current method should establish what was requested, by whom and with which response, without assuming that the earlier tool is maintained today.
Technical 03
Google guidelines: turn reading into page-level checks
Reading a rule does not repair a page. Connect each defect to a test, an owner and observable evidence after a change.
Technical 04
Multiple domains: choose redirects, canonicals or genuinely separate sites
Start with the purpose of each address. Another domain only deserves an independent site when it offers a distinct product, audience or practical service.
Technical 05
Paid links: separate advertising from independent evidence
A commercial link can help a reader when it is relevant and clearly identified. Treat it as an advertising relationship rather than independent proof of quality.
Technical 06
Page speed: measure reading, responsiveness and stability
A fast page becomes readable, responds to input and keeps its layout stable. A laboratory result is diagnostic; real experience also depends on devices and networks.
Technical 07
From Flash to JavaScript: make content accessible beyond the interface
Old Flash sites raised a question that still matters: does the content exist outside the animation? A JavaScript interface also needs accessible answers and stable URLs.
Technical 08
AI search and SEO: make information accessible and verifiable
Search interfaces change, but accessible, accurate and sourced information is still concrete work. No special markup guarantees inclusion in a generative answer.
Technical 09
WordPress foundations for durable, secure publishing
A 2009 book announcement is not current product documentation. This preparation method focuses on content, URLs and responsibilities that need to last.
Technical 10
301, 302, 307 and 308: choose a redirect and verify the journey
A redirect describes a move and whether it is temporary or permanent. The correct choice also depends on the request method and destination service.
Technical 11
XML sitemaps: audit URLs before submission
A sitemap is a discovery list. Build it from published pages, then compare the list with HTTP responses and canonical decisions.
Technical 12
SEO migrations: acceptance checks and a rollback plan
A migration should preserve content, links and user journeys. Map destinations before switching and retain a version you can restore.
Technical 13
Syndicated content: decide which version to keep
A wire story, press release and republication can share passages while serving different needs. Clarify each page’s role before deleting or consolidating it.
Technical 14
Multi-domain sitemaps: keep ownership and routing clear
A group of websites may share infrastructure. Central generation can help operations, but every URL still needs the correct hostname and owner.
Technical 15
Business video platforms: compare access, export and playback
The right choice depends on private training, public communication or commercial distribution. Test the complete journey and an exit from the service before committing.
Technical 16
Choosing low-code without locking in your data
Low-code can shorten development, but access, maintenance and export still matter. Evaluate a small representative journey before building the entire system.
Technical 17
No-code: move from prototype to maintainable operation
A prototype demonstrates an idea; a production tool must handle errors, access and change. Decide what a pilot needs to teach before entrusting it with a real process.
Technical 18
Virtual showrooms: useful discovery beyond the visual effect
Immersive spaces should help people compare or understand products. Preserve a simple accessible journey when a 3D scene is unavailable.
Technical 19
Business SEO audits: deliver decisions, not a score sheet
A useful audit connects each issue to a page, a possible effect and a verifiable action. A long generic recommendation list is not an implementation roadmap.
Technical 20
Quality web design: a visible, measurable acceptance plan
A website should stay readable and functional under different conditions. Turn design intentions into checks on actually rendered pages.
Technical 21
Marketing databases: define quality before integration
Usable databases need definitions, permissions and checks. Before connecting a tool, explain which information is necessary and who can correct it.
Technical 22
Digitising videotapes: preserve a file, not only a DVD
Digitisation should retain content that can be consulted and reused. Define source condition, delivered formats and checks before choosing a provider or storage medium.
Technical 23
Publisher archives: make older articles genuinely accessible
A sitemap does not replace editorial navigation. Build useful paths to older material and verify that each route reaches the correct document.
No results. Try another word or clear the filter.