Skip to content

Commit f34b1a9

Browse files
authored
fix: Add '@' prefix to search engine shortcuts in guide
Updated examples to include '@' prefix for search shortcuts. Signed-off-by: JM (Jason Meridth) <[email protected]>
1 parent 8fe8c14 commit f34b1a9

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

content/posts/2025-06-08-chromium-search-engines.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,24 +8,26 @@ tags:
88
- developer-experience
99
---
1010

11+
UPDATE (7/31/2025): Prefixing the search shortcut value with an `@` ensures the browser doesn't mistake it for a regular search instead of a shortcut.
12+
1113
TL;DR: Managing search engines in Chromium-based browsers can significantly enhance your browsing efficiency. Here's how to do it. aka chrome://settings/searchEngines
1214

1315
I am a keyboard user more than a mouse user. I don't tend to use bookmarks in my browser. I prefer to use "shortcuts" in my browser's address bar to quickly access different websites. The aliases are entries into my Chromium-based browser's settings, search engines. This allows me to type a keyword followed by a search term to quickly navigate to the desired site or perform a search.
1416

15-
Example: typing `blog` goes to this repository, https://github.com/jmeridth/jmeridth.github.io. Another option typing `tags`, tabbing and then typing `go` will result in the url https://jmeridth.github.io/tags/go.
17+
Example: typing `@blog` goes to this repository, https://github.com/jmeridth/jmeridth.github.io. Another option typing `@tags`, tabbing and then typing `go` will result in the url https://jmeridth.github.io/tags/go.
1618

1719
Both of these can be created by going to the search engines settings in your browser. In Chromium-based browsers, you can access this by navigating to `chrome://settings/searchEngines`. Here, you can add new search engines or edit existing ones.
1820

1921
To add a new search engine, click on "Add" and fill in the following fields:
2022
- **Search engine**: A name for the search engine (e.g., "Blog").
21-
- **Keyword**: A keyword that you will type in the address bar to trigger this search engine (e.g., "blog").
23+
- **Keyword**: A keyword that you will type in the address bar to trigger this search engine (e.g., "@blog").
2224
- **URL with %s in place of query**: The URL you want to navigate to, with `%s` as a placeholder for the search term (e.g., `
2325

24-
For `blog`, the Name would be `blog`, Shortcut would be `blog`, and URL would be `https://github.com/jmeridth/jmeridth.github.io`.
26+
For `blog`, the Name would be `blog`, Shortcut would be `@blog`, and URL would be `https://github.com/jmeridth/jmeridth.github.io`.
2527

2628
![Chromium Search Engine Blog](/img/chromiumsearchengine_blog.png)
2729

28-
For `tags`, the Name would be `tags`, Shortcut would be `tags`, and URL would be `https://jmeridth.github.io/tags/%s`.
30+
For `tags`, the Name would be `tags`, Shortcut would be `@tags`, and URL would be `https://jmeridth.github.io/tags/%s`.
2931

3032
![Chromium Search Engine Tags](/img/chromiumsearchengine_tags.png)
3133

0 commit comments

Comments
 (0)