Colquhoun.AI
← All guides

Research Guides

Keep a Literal Plus in a Shared Research Query

· Colquhoun.shop editorial

A shared research URL can open a working search page and still change the term the researcher meant to send. One easy case to miss is a literal plus sign: in a form-style query, an unescaped plus can be read as a space. Test the decoded values before filing a finding about the search engine or citing the resulting evidence.

1. Identify the parser that reads the link

The WHATWG URL Standard's form-encoded parsing algorithm replaces literal plus signs with spaces before percent-decoding the values. The companion serializer represents a space as a plus and escapes a plus that is part of the value. This describes form-style query processing, including URLSearchParams, not a rule for rewriting every plus sign anywhere in a URL.

Check the destination's documented contract. The page could use another parser, or a later processing step could normalize its query. Know which representation you observed before assigning the cause.

2. Compare two values that differ by one character

Use a fictional library's search term Plan+2026 and a separate test for Plan 2026. On a standard form-style path, q=Plan%2B2026 represents the first value and q=Plan+2026 represents the second. If a copied link for the first value contains a raw plus instead, the receiving parser can read the second term and quietly deliver other results.

In JavaScript, constructing new URLSearchParams({q: 'Plan+2026'}).toString() serializes the raw value as q=Plan%2B2026. Pass the raw term, not an already escaped value. If you pass Plan%2B2026 as the raw value, serialization escapes the percent sign too and changes what a single parse returns.

3. Trace the values rather than counting successes

Exercise the journey from a newly opened link, not just the search form that generated it. The form might keep the right value in memory even though a copied address does not. A 200 response establishes that a page was served, not that it received the intended term.

4. Keep this test within the link's real purpose

Use a synthetic term rather than exposing private queries in screenshots, logs or external examples. Do not run a broad URL cleanup to fix a single query field. This worksheet does not establish that another site's query parser behaves the same way or that a modified link is the right canonical URL.

Retest both cases after repairing the link builder. Confirm that the actual results continue to distinguish the terms if the destination's documented search behavior calls for that distinction. Some search engines deliberately normalize punctuation after decoding, which is a separate layer from URL serialization.

5. Write a narrow completion note

A useful report is: “In the sampled share flow, a literal plus is serialized as %2B and the receiving page decodes the original term. The space fixture remains a separate decoded value.” State whether you checked the search results or only the parameter round trip. That protects a research citation from pointing to a different query than the one its author used.

This guide describes the built-in Web Reader and Keyword Density behavior verified for this publication. Available data depends on the page response; these tools do not measure visits or search rankings.