Then and now
Where it stood in June, and where it stands today.
There is no old screenshot to show here, because there was nothing to screenshot. Search Console has rows for locul.ai from 14 June 2026. The earliest complete 28 days, 14 Jun to 11 Jul 2026, cover the 23 days before the first article and the first five days after it. That window is the “then”.
Figure 1
Then against now, the same three measures
| Measure | 14 Jun to 11 Jul 2026 | 9 Sept to 6 Oct 2026 |
|---|---|---|
| Clicks | 0 | 197 |
| Impressions | 150 | 21,380 |
| Average position | 10.7 | 8.8 |
| Click-through rate | 0% | 0.92% |
Clicks in 28 days
197
was 0 in June and early July
from none at all
Impressions in 28 days
21,380
was 150 in June and early July
about 143 times as many
Average position
8.8
was 37.8 in the 28 days before
29.0 places better than the 28 days before
The fairer comparison for a site this young is the 28 days immediately before (12 Aug to 8 Sept). Against that window clicks are 4.4 times higher, from 45 to 197. Impressions doubled, from 10,654 to 21,380. Average position moved from 37.8 to 8.8.
One honest caveat. Any new site goes from nothing to something, so “from zero” is not an achievement on its own. Read the first window as a dated starting line, and judge the site on the weeks that follow, which are all in the chart below.
The full picture
Sixteen weeks, week by week. Dip included.
From 14 June 2026 to 6 October 2026, 115 days, locul.ai earned 267 clicks from 35,151 impressions in Google Search. The first click was recorded on 15 July 2026, eight days after the first article. The best single day so far was 22 September 2026, with 15 clicks.
Figure 2
locul.ai in Google Search, per week
Hover the chart, or focus it and use the arrow keys, to read any week.
Show all 16 weeks as a table
| Week | Clicks | Impressions | Position |
|---|---|---|---|
| 15 Jun to 21 Jun 2026 | 0 | 4 | 1.5 |
| 22 Jun to 28 Jun 2026 | 0 | 18 | 6.3 |
| 29 Jun to 5 Jul 2026 | 0 | 55 | 5.4 |
| 6 Jul to 12 Jul 2026 | 0 | 87 | 17.9 |
| 13 Jul to 19 Jul 2026 | 2 | 227 | 23.6 |
| 20 Jul to 26 Jul 2026 | 3 | 400 | 28.8 |
| 27 Jul to 2 Aug 2026 | 2 | 822 | 33.2 |
| 3 Aug to 9 Aug 2026 | 18 | 1,058 | 31.0 |
| 10 Aug to 16 Aug 2026 | 3 | 2,004 | 50.1 |
| 17 Aug to 23 Aug 2026 | 10 | 2,468 | 51.8 |
| 24 Aug to 30 Aug 2026 | 7 | 3,176 | 42.6 |
| 31 Aug to 6 Sep 2026 | 18 | 2,355 | 17.0 |
| 7 Sep to 13 Sep 2026 | 30 | 3,483 | 11.6 |
| 14 Sep to 20 Sep 2026 | 24 | 3,261 | 10.9 |
| 21 Sep to 27 Sep 2026 | 71 | 5,893 | 8.0 |
| 28 Sep to 4 Oct 2026 | 59 | 7,502 | 7.8 |
Switch the chart to average position and you will see the part most new-site stories leave out. Through August the position got worse, not better: 28.5 in July, then 44.6 in August. Impressions were climbing at the same time, from 1,252 to 9,382. The articles were being shown for many more searches, most of them far down the results.
Then it turned. In the week of 31 August the weekly average was 17, and in September the month averaged 9.7. Clicks followed: 6 in July, 42 in August, 174 in September.
Figure 3
Month by month, July to September 2026
| Month | Clicks | Impressions | Position |
|---|---|---|---|
| July 2026 | 6 | 1,252 | 28.5 |
| August 2026 | 42 | 9,382 | 44.6 |
| September 2026 | 174 | 18,331 | 9.7 |
One article shows the same curve on its own. This is the page that now earns the most clicks on the site, published on 28 July 2026, on four single days.
Figure 4
One new article, four days in its first ten weeks
| Day | Impressions | Position | What it shows |
|---|---|---|---|
| 1 August 2026 | 99 | 30.2 | Four days after publication |
| 21 August 2026 | 20 | 58.7 | Three weeks in, far down |
| 5 September 2026 | 16 | 6.9 | Back, on page one |
| 7 October 2026 | 454 | 5.6 | Two days before this page was written |
If you had judged that article on 21 August you would have called it a failure. Two weeks later it was on page one. If you run a new blog, the practical lesson is to wait before you decide anything about an article. This one needed about five weeks. Our study of 633 new articles has the wider numbers on that wait.
The niche
What ranked first for a notes tool, and what did not.
Locul sits in a crowded space: note-taking apps, second brain methods, and AI memory. The obvious searches to want are the category ones, such as “second brain app”. Three months in, those are not where the clicks come from.
What ranks on page one is narrower. People who already use a named tool and are choosing between two features, or two tools, are the readers the site reaches today.
Figure 5
Searches that name two tools sit on page one
| Query | Impressions | Clicks | Position |
|---|---|---|---|
| obsidian bases vs dataview | 102 | 1 | 6.6 |
| notebooklm vs obsidian | 76 | 0 | 9.0 |
| obsidian vs notebooklm | 56 | 0 | 9.6 |
| obsidian dataview vs bases | 53 | 1 | 7.9 |
| claudian vs copilot obsidian | 38 | 1 | 3.9 |
Figure 6
Category searches are still far down
| Query | Impressions | Clicks | Position |
|---|---|---|---|
| notebooklm alternatives | 73 | 0 | 41.5 |
| second brain app | 66 | 0 | 56.6 |
| best apps for second brain | 35 | 0 | 64.8 |
Two more things in the data surprised us. The article with the most clicks is not about notes at all. It is a guide to choosing a local language model, a neighbouring topic that the same readers care about. And the third most clicked page on the whole site is a German translation.
Figure 7
Locul's top pages by clicks, last 28 days
- /blog/best-local-llm
36 clicks · 5,480 impressions · position 6.8
- /
34 clicks · 839 impressions · position 4.0
- /de/blog/ai-second-brain-setup
29 clicks · 767 impressions · position 6.7
- /blog/best-obsidian-ai-plugins
8 clicks · 1,061 impressions · position 6.4
- /skills/
7 clicks · 238 impressions · position 11.8
- /blog/obsidian-ai-plugins
6 clicks · 607 impressions · position 7.3
- /blog/obsidian-bases-plugin
6 clicks · 859 impressions · position 6.4
- /blog/dataview-obsidian-plugin
5 clicks · 700 impressions · position 9.8
The German versions are worth a line of their own. 51 of the 103 English articles have one. In the last 28 days, 43 German pages earned 46 clicks from 1,852 impressions at an average position of 7.3. That is a click-through rate of about 2.5%, against 0.9% for the site as a whole. Fewer people search in German, and far fewer pages compete for them.
How we run it
We do not open a dashboard. We ask Claude.
Locul's Search Console is connected to Murkuz once. After that the work happens inside Claude. Murkuz hands Claude the real rows for the site, with the window and the source attached, and Claude does the reading: which queries, which pages, what changed, what to do next. We draft the articles and the edits in the same conversation.
The drafts then go into the Murkuz CMS, which renders Locul's blog. On 9 October 2026 it held 103 published English articles for the site. That part of Murkuz is an add-on we enable on request, and it is covered further down. The loops themselves need only the connector.
Figure 8
From Search Console row to published article, and back
Source
Google Search Console
Clicks, impressions and positions for every Locul page and query.
Connector
Murkuz
Hands those rows to the agent: filtered, sorted, paginated and sourced.
Agent
Claude
Runs the three loops, decides what to write or merge, and drafts it.
Add-on, on request
Murkuz CMS
Holds the drafts and their German versions, and renders the published articles.
Result
The live blog
The article goes live on locul.ai/blog and starts collecting impressions.
Two to four weeks later the new rows are in Search Console, and the next pass of the loops starts from them.
The method
Three loops, repeated every two to four weeks.
The method is the same one we use on LigoSocial, a site with about ten times the clicks. Three questions, asked again and again of fresh data. On a new site the weight sits on the first loop, because there is little to merge and little to tighten until pages rank. We show all three below, including the one where we have no result to report yet.
Figure 9
The three loops as one cycle
- 01New articlesWhich searches about notes, memory and AI tools do we show up for with no page that answers them properly?
Search_AnalyticsKeyword_IdeasCompetitor_Gap - 02CannibalisationWhere are two of our own articles answering the same search and splitting the result?
Live_Cannibalization - 03Easy wins on top pagesWhich queries does a page that already ranks sit far lower for than it does on average?
Live_Quick_WinsSearch_Analytics
Repeat every 2 to 4 weeks
01New articles
A new site has no queries to read, so this loop cannot start from Search Console. It starts from keyword research. As rows arrive, it switches to the site's own data: searches the site is shown for with no page that answers them directly.
Between 7 July 2026 and 28 September 2026 we published 103 English articles: 57 in July, 43 in August and 3 in September. Figure 2 shows what followed: impressions first, clicks about two months behind.
Figure 10
What the articles earned in the last 28 days
| Measure | Context | Blog articles |
|---|---|---|
| Articles with at least one impression | 147 | |
| Clicks | of 203 site-wide | 145 |
| Impressions | of 21,704 site-wide | 19,757 |
| Average position | 8.9 |
So 145 of the site's 203 clicks in that window landed on an article. Of the rest, 34 landed on the home page, and searches for the name Locul account for 29 clicks. The most recent article is “Best MCP Servers in 2026: Picks by Job for Claude Code, Cursor and Codex”, 3,362 words, published on 28 September 2026. It is too new to judge, for the reason Figure 4 gives.
02Content cannibalisation
Publish a hundred articles in two months and some of them will answer the same search. Google then has to choose between your own pages, and often ranks neither as well as it would rank one clear page. The second loop finds those collisions.
Here is one we have already acted on. Two articles covered AI plugins for Obsidian, with nearly the same address. In the last 28 days both were on page one, a place apart.
Figure 11
Two articles, one topic: the pair we merged
- /blog/best-obsidian-ai-plugins
8 clicks · 1,061 impressions · position 6.4
- /blog/obsidian-ai-plugins
6 clicks · 607 impressions · position 7.3
The second address now redirects to the first. The last day Search Console recorded an impression for the old address was 3 October 2026. In the four days after that, the surviving page was shown 54, 37, 58, 54 times a day at average positions of 6.4, 4.8, 4.4, 5.2.
That is four days of data, and it proves nothing yet. In the week before, the same page averaged between 5.1 and 6.0 a day, so the early readings are close to where it already was. We will read this pair again at the next pass, and that later number is the one that counts.
The loop also has open work. On 9 October 2026 the connector found 3 queries where two or more Locul pages appeared for the same search in the last 28 days, counting queries with at least 50 combined impressions. One of the three is the site's own name, where several pages showing together is normal. This is one of the other two.
Figure 12
Still open: two of our pages for "second brain app"
- /blog/best-second-brain-apps-compared46 impr. · pos. 65.3
- /blog/best-ai-second-brain-apps22 impr. · pos. 37.6
Two list articles about second brain apps, both far down, and Google shows the weaker one more often. This is the category search from Figure 6. One strong page has a better chance there than two thin ones, so this pair is next on the list.
03Easy wins on top pages
The third loop takes a page that already ranks, lists every query it ranks for, and looks for the ones it is weak on. Here is the site's top article. Over the last 28 days it earned 36 clicks from 5,480 impressions at an average position of 6.8:
/blog/best-local-llm
Figure 13
Reverse-engineering one page: where it ranks for each query
- best local llm for general use8 impr.pos. 5.55.5
- best local llm for 32gb ram9 impr.pos. 7.97.9
- best llm for everyday use17 impr.pos. 8.18.1
- best local llm for coding 8gb vram11 impr.pos. 8.58.5
- best local llm models28 impr.pos. 9.49.4
- best local llm for 8gb vram9 impr.pos. 14.114.1
- local llm47 impr.pos. 23.323.3
- best local llm30 impr.pos. 27.627.6
- best local llm 16gb vram9 impr.pos. 45.945.9
The pattern is specific. The page is on page one for a named amount of memory: 8GB for coding, 32GB of RAM. It is at position 45.9 for 16GB. That tier is a search of its own, and the page does not answer it well enough yet. It is also on page three for the two shortest phrasings, “local llm” and “best local llm”, which carry the most impressions in the list.
The edit is small. Give 16GB a section of its own, and answer the short question in the first paragraph. Leave the rest alone, because the rest is working.
We do not have a finished example of this loop on Locul. No page here has yet had its weak queries worked in and then been measured two to four weeks later, so there is no before-and-after position to show. The 16GB edit above is the first candidate. Site-wide, the connector found 3 queries at position 15 or better with at least 100 impressions in 28 days. On a site this young, that list is short.
Figure 14
Queries close enough to move
| Query | Impressions | Clicks | Position |
|---|---|---|---|
| what is notion ai | 186 | 0 | 9.3 |
| obsidian bases vs dataview | 102 | 1 | 6.6 |
| locul | 363 | 29 | 4.7 |
Automate it
You do not need us in the room. You need the prompt.
None of this depends on a person remembering to do it. Murkuz gives you the skill file for it: a prompt that Claude runs as a loop of its own, on your machine or wherever you run your agents. Connect your sites, hand Claude the prompt, and it works through all three loops and comes back with one prioritised list.
Here is a starter version you can paste into Claude today, with the Murkuz connector attached.
You have the Murkuz connector. Work on one site: <your site>.
Use the last 28 days unless I say otherwise, and state the window and the
property with every number you report.
Loop 1, new articles
- Call Search_Analytics by query, sorted by impressions. List queries with
real impressions where no page of ours answers the search directly.
- For the strongest five, call Keyword_Ideas to find the neighbouring terms.
- Propose one article per gap: working title, target query, the questions it
must answer, and the existing pages it should link to.
Loop 2, cannibalisation
- Call Live_Cannibalization. For each query where two or more of our pages
compete, name the page that should own it and say what to do with the
others: merge, redirect, or re-angle towards a different query.
Loop 3, easy wins on top pages
- Call Search_Analytics by page, sorted by clicks, and take the top ten.
- For each, call Search_Analytics by query filtered to that page. Find the
queries where it ranks clearly worse than its own average.
- Say exactly where to work each weak query in: a heading, an answer near the
top, or a new section. Do not rewrite what already ranks.
- Call Live_Quick_Wins for queries just off the top three, and add those.
Finish with one prioritised list of changes, biggest expected gain first.
Do not invent a number. If a tool returns nothing, say so.
Run this again in two to four weeks and compare against today.Every tool it names is in the connector tool reference. Reading your own Search Console data is never metered. Keyword_Ideas is the one research call in the prompt, and it uses research credits.
Add-on, on request
Publishing your blog through Murkuz
Locul's articles and their German versions are uploaded to Murkuz and rendered on its blog by Murkuz, and each one is audited and optimised on the way. That keeps the writing, the publishing and the measuring in one place, which is why the loops above are quick for us to act on.
This is not a self-serve feature and you will not find it in the app after signing up. It is available on request as an add-on. If you want your blog published through Murkuz, contact support and we will enable it for your account.
Method and limits
What these numbers are, and what they are not
- Source. Google Search Console for locul.ai, web search, read through the Murkuz connector on 9 October 2026. Bing is not included in any figure on this page.
- Windows. “Now” is 9 Sept to 6 Oct 2026, the latest complete 28 days on the pull date. “Then” is 14 Jun to 11 Jul 2026, the earliest complete 28 days in the property. The weekly chart uses complete Monday to Sunday weeks. The loop examples use the connector's last-28-days window on the pull date, 11 Sept to 8 Oct 2026, whose final day was still filling in.
- Small numbers. A page with 36 clicks in a month can swing on a handful of searches. Treat single rows as examples, and the weekly chart as the result.
- Average position. Weighted by impressions across every query, device and country. It is not a rank-tracker rank, so read changes in it rather than the absolute number.
- No causal claim. There was no control group. A new site grows from zero whatever you do, and we cannot separate the loops from that.
- First party. Locul is built by the same team as Murkuz. We are our own customer here.
FAQ
Questions about this case study
Is Locul a Murkuz customer?
Locul is built by the same team that builds Murkuz, so this is a first-party case study. We use Murkuz on Locul exactly as a customer would: Search Console connected once, questions asked from inside Claude.
Where do the numbers come from?
Every number is Google Search Console data for locul.ai, web search, read through the Murkuz connector on 9 October 2026. The daily series was checked against a second pull grouped by device, and the totals matched.
How long did a new site take to get its first Google click?
The first article went live on 7 July 2026 and the first click from Google Search was recorded on 15 July 2026, eight days later. The first week with more than ten clicks was the week of 3 August 2026.
Why did average position get worse in August before it got better?
In August the new articles began to appear for many more searches, mostly deep in the results, so impressions rose from 1,252 to 9,382 while average position went from 28.5 to 44.6. In September the same site averaged 9.7. We show the dip because it is part of the record, and we do not claim to know exactly why Google moved the pages when it did.
Did Murkuz cause the growth?
We cannot prove that, and we do not claim it. There was no control group, and a new site grows from zero whatever you do. What we can say is that these are the loops we ran, through Murkuz, over the period the chart covers, and that the chart is the real result.
How often should you run an SEO loop like this?
We repeat all three loops every two to four weeks. Search Console data needs a couple of weeks to settle after a change, so running them more often mostly measures noise.
Can Murkuz publish my blog as well?
Yes, on request. Murkuz includes a CMS that can hold your articles and render your blog, with each article audited and optimised. It is not a self-serve feature: contact support and we will enable it for your account as an add-on.
Want an older site? The LigoSocial case study runs the same three loops on a blog with ten months of data. The keyword cannibalisation guide covers loop 2 in depth.