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
Concrete methods for deciding, building, publishing and measuring. Every guide includes a worked example, an infographic and an actionable checklist.
96 guides
Technical 01
Preventing crawling and requesting exclusion from results are different decisions. First decide whether a page should remain available to readers.
Technical 02
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.
Measurement 03
An earlier depiction of the top three positions does not describe every current journey. Observe results for a specific question, device and context.
Technical 04
Reading a rule does not repair a page. Connect each defect to a test, an owner and observable evidence after a change.
Strategy 05
An agency’s challenge is not just offering more channels. It is completing a decision when several disciplines and systems are involved.
Editorial 06
Someone searching your name may want to check a product, find an account or solve a problem. Identity helps them recognise the answer, but it also needs to be verifiable.
Strategy 07
A longer query can reveal a specific constraint. Length alone proves neither low competition nor better conversion. Build pages around distinct, verifiable needs.
Measurement 08
A search-engine map describes a territory, period and method. Before making a decision today, identify all three rather than extrapolating an old graphic.
Editorial 09
A useful company blog answers the questions that delay a purchase or make a product difficult to use. Begin with recurring customer needs, then decide what evidence will resolve them.
Strategy 10
A monthly fee tells you little without a scope. Compare deliverables, labour, technical dependencies and acceptance criteria before comparing two headline prices.
Technical 11
Start with the purpose of each address. Another domain only deserves an independent site when it offers a distinct product, audience or practical service.
Editorial 12
A title should help a reader recognise the answer. The brand identifies the publisher; it should not displace the subject or become a list of repeated keywords.
Strategy 13
Search volume can sort candidates. It cannot replace an understanding of the task, country, language and answer your site is able to provide.
Strategy 14
A useful strategy connects an audience, a substantiated offer, a library of answers and the ability to maintain them. A wishlist of positions is not that plan.
Technical 15
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 16
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 17
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.
Measurement 18
Excellent Analytics belonged to an earlier generation of tools. The underlying need remains: turn an export into decisions without losing definitions or provenance.
Measurement 19
A branded query may mean purchasing, signing in or resolving a problem. The right destination depends on the task, not merely the presence of the brand name.
Editorial 20
A professional presence does not require publishing everything. Focus on exposed information, its context and practical ways to correct mistakes.
Strategy 21
Residents should not need to understand an organisation chart to find a public service. Organise the answer around what someone needs to do.
Strategy 22
A destination is chosen under real constraints: transport, season, budget, availability and accessibility. Attractive imagery should lead to usable answers.
Editorial 23
A glossary helps when it explains a term at the moment someone needs it. It should not create a separate page for every variation of a word.
Strategy 24
A niche is more than a long keyword. It is a context, constraint or audience whose needs your service can address differently.
Measurement 25
Revenue attributed to a campaign is not profit. A useful calculation separates spend, conversion, contribution and uncertainty.
Strategy 26
A good collaboration makes work, access and responsibility visible. Ask for inspectable deliverables rather than a promised position.
Technical 27
Search interfaces change, but accessible, accurate and sourced information is still concrete work. No special markup guarantees inclusion in a generative answer.
Technical 28
A 2009 book announcement is not current product documentation. This preparation method focuses on content, URLs and responsibilities that need to last.
Editorial 29
A listing should help a reader decide whether a viewing makes sense. Accurate features, location and contact conditions matter more than a string of adjectives.
Editorial 30
A release explains something new. A list of distribution platforms cannot replace a precise fact, evidence and a contact route.
Editorial 31
An account is useful when readers know why to follow it. Platforms change; a consistent promise and responsibility for publication remain important.
Measurement 32
A visit, an enquiry and a customer relationship are different stages. Connecting them can improve the response when collection is limited and events are precisely defined.
Strategy 33
An outcome-based arrangement needs a measured event and clear responsibilities. An isolated ranking can reward work that does not actually help the client.
Strategy 34
A credential can attest a particular assessment. It does not guarantee every deliverable or a position in search results.
Editorial 35
Google Instant is part of search history. Its attention debate remains useful when designing a site search that lets readers understand and choose.
Editorial 36
Digitising an object does not explain what it represents. A reliable record connects the object with provenance, dates, rights and access.
Technical 37
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 38
A sitemap is a discovery list. Build it from published pages, then compare the list with HTTP responses and canonical decisions.
Technical 39
A migration should preserve content, links and user journeys. Map destinations before switching and retain a version you can restore.
Measurement 40
A backlink total depends on an index and its filters. Compare definitions before concluding that a tool is wrong or a campaign succeeded.
Technical 41
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 42
A group of websites may share infrastructure. Central generation can help operations, but every URL still needs the correct hostname and owner.
Measurement 43
A chart depends on its calendar. Align days, time zones and metric definitions before commenting on growth or decline.
Measurement 44
Two accurate reports can show different volumes. Search-result clicks and sessions recorded after arrival have different definitions and collection methods.
Strategy 45
A seasonal page should help people choose at the right moment. Coordinate stock, delivery information and content updates instead of publishing everything at the last minute.
Editorial 46
Video needs readable context, an identifiable answer and reliable playback. A media file alone does not establish a useful search destination.
Editorial 47
A cultural document becomes more useful when provenance, rights and limitations are readable. Build a record that helps both readers and discovery systems.
Strategy 48
Coordinated linking campaigns form part of search history. Their useful lesson concerns the difference between temporary visibility, reputation and durable value.
Measurement 49
Suggestions can reflect language patterns, data and product decisions. Investigate differences with a protocol that avoids generalising from one search.
Strategy 50
An old audience statistic does not describe your publication today. Separate passing visits, useful journeys and evidence of continued readership.
Measurement 51
A suspicious curve can result from collection, calculation or display. Separate these layers before turning a visual anomaly into a commercial conclusion.
Editorial 52
An editorial community needs understandable rules. Popularity, recommendations and moderation should not be mistaken for factual verification.
Editorial 53
Paid content should explain its origin and deliver a verifiable answer. Prepare the collaboration before writing rather than treating quality as a final link-placement step.
Strategy 54
Travellers may have limited time and an unreliable connection. Prioritise immediate decisions: access, opening times, booking and conditions.
Measurement 55
A normalised curve describes relative interest within a selected scope. It does not automatically translate a search into customers or sales volumes.
Strategy 56
VR is useful when it addresses a specific learning difficulty. Compare it with a simpler approach before funding scenes, headsets and deployment.
Strategy 57
A website starts with user needs, content and responsibility. A clear brief avoids discovering at handover that nobody controls the domain or can edit the copy.
Strategy 58
Ask candidates to answer the same brief. A portfolio can demonstrate taste, but does not establish maintenance quality, account ownership or usable journeys.
Editorial 59
An identity should remain recognisable in real applications. Define rules that help a team produce consistent interfaces, documents and illustrations.
Strategy 60
Useful research reduces a specific uncertainty. Before collecting opinions, write down the decision, hypotheses and findings that would change your strategy.
Editorial 61
Clean recording is one stage of a podcast project. The brief also needs preparation, editing, transcription and the files required for publication.
Technical 62
The right choice depends on private training, public communication or commercial distribution. Test the complete journey and an exit from the service before committing.
Strategy 63
A camera alone does not make a hybrid event. Prepare two understandable journeys and organise questions, accessibility and fallback arrangements.
Technical 64
Low-code can shorten development, but access, maintenance and export still matter. Evaluate a small representative journey before building the entire system.
Technical 65
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.
Editorial 66
Useful language versions adapt answers, units and journeys. Give translators context and verify the published page rather than approving only a translated file.
Editorial 67
A professional profile should explain your role and work. Replace generic adjectives with understandable accomplishments, honest limits and deliberate contact choices.
Strategy 68
Discovery should lead to an understandable learning resource. Prepare levels, objectives and exercises before deciding where to promote it.
Measurement 69
A sale attributed to advertising is not automatically profitable or incremental. Include costs, returns and uncertainty in the campaign decision.
Technical 70
Immersive spaces should help people compare or understand products. Preserve a simple accessible journey when a 3D scene is unavailable.
Strategy 71
A funnel should support an informed decision and a reliable action. Clarify the offer, requested information and follow-up before choosing a platform.
Strategy 72
SMS reaches a personal channel. Before discussing performance, check permission, message relevance and a simple way to stop further marketing.
Measurement 73
A useful result depends on the question and context. Define your assessment before selecting examples that seem to confirm an opinion about a search engine.
Technical 74
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 75
A website should stay readable and functional under different conditions. Turn design intentions into checks on actually rendered pages.
Editorial 76
A video commission should describe its intended outcome and uses. Define formats, rights, revisions and acceptance before comparing suppliers.
Editorial 77
An illustration should clarify a question. Before producing an infographic, decide what readers need to compare, understand or verify.
Strategy 78
A useful plan explains whom you serve, what you test and how you will decide afterwards. Channels follow those choices rather than replacing them.
Technical 79
Usable databases need definitions, permissions and checks. Before connecting a tool, explain which information is necessary and who can correct it.
Editorial 80
Packaging and online listings should describe the same product coherently. Check readability, specifications, variants and claims instead of treating each format independently.
Strategy 81
Training should make a skill observable. Compare programmes, exercises, assessment and follow-up instead of choosing only a list of fashionable tools.
Strategy 82
A paid-search brief should connect need, advert, destination and offer economics. An agency or platform does not replace those decisions.
Measurement 83
Metrics from different providers are not interchangeable. A score can help organise observations, but does not certify editorial reliability or future rankings.
Strategy 84
A promotion code should deliver an understandable benefit. Define eligibility, exclusions and final price so the discount exists beyond a headline promise.
Measurement 85
An exchanged service has costs and limitations. Describe commitments, estimated value and delivery evidence before presenting barter as an advantage.
Strategy 86
An on-site activation needs an audience, appropriate permission and a clear next step. A crowd or photograph does not establish effectiveness.
Editorial 87
Advertising covers several responsibilities. Understand who plans strategy, writes, produces, distributes and evaluates before assembling a team.
Strategy 88
A provider needs to know what it can resolve and what it must escalate. Quality depends on the brief, information access and handling of difficult cases.
Technical 89
Digitisation should retain content that can be consulted and reused. Define source condition, delivered formats and checks before choosing a provider or storage medium.
Editorial 90
Manual selection can clarify a subject while missing another interpretation. Test specific tasks rather than a curator’s reputation or the length of a link list.
Editorial 91
Finding an article and establishing a fact are different tasks. Define the scope, open the publications and assemble a verifiable timeline.
Editorial 92
An aerial view is a dated observation rather than a live camera. Record what it shows and which conclusions it cannot establish.
Strategy 93
A local profile should help people verify where to go, when to visit and which service is available. Prepare accurate information before trying to expand visibility.
Measurement 94
A query volume is neither a customer count nor a visitor target. Preserve measurement settings and use estimates to decide which questions deserve an answer.
Measurement 95
A calculator can give an exact answer to a badly specified question. Write down the units and calculation basis before choosing the tool.
Technical 96
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.