Coder Legion - Recent posts tagged search

What Access an SEO Audit Actually Needs | FloxoLab

Fri, 30 Oct 2026 15:50:00 +0000

Direct answer: A diagnosis-only SEO audit normally needs the public website URL and Restricted access to Google Search Console. GA4 Viewer access is optional. CMS, hosting, registrar, passwords, billing, and Search Console ownership are implementation or control privileges, not audit requirements.

Access is where trust quietly breaks down between a business and whoever does its SEO. The request usually arrives bundled and casual: send over your website login, your hosting, your Google accounts, and we will take it from here. Most owners hand it over because they do not know which parts are actually needed and which are just convenient for the agency.

What an audit actually needs

An audit is a diagnosis, not surgery. To find the problems holding a site back, the only things genuinely required are your URL and the ability to read your own search data. That is it.

Access or input	Audit need	Safe scope
Public website URL	Required	No login. Include priority pages and any staging boundary.
Search Console	Usually required	Restricted user. This can view most reports but cannot administer the property or submit a sitemap.
GA4	Optional	Viewer. Add No Cost Metrics or No Revenue Metrics restrictions when those values are outside the audit scope.
Business context	Helpful	Priority services, target geography, intended queries, and known competitors.
CMS, hosting, or registrar	Not needed for diagnosis	Grant separately only for an approved implementation task with an owner and end date.

Notice what is not on that list: no website admin login, no hosting panel, no domain registrar, no passwords. A diagnosis is built from reading data, not from holding the keys to the building.

This holds even for the deeper technical part of an audit. Crawling the whole site to surface broken internal links, redirect chains, duplicate or missing titles, and a bloated sitemap is done with a crawler that visits your pages exactly like any other visitor, over the public web. It reads what is already published, so it needs no login at all.

The next step is to combine that public crawl with read-only Google evidence. The Screaming Frog and Search Console audit workflow shows how to reconcile the URL sets without granting implementation access.

How to grant read-only access safely

Both Google tools have a low-privilege viewing role. Add a specific email, choose the lowest role that still exposes the required reports, and remove it when the work is done. These roles do not provide control over your website, domain, or Google account.

Search Console: the Restricted role

In Search Console, open Settings > Users and permissions, click Add user, enter the email you were given, and choose Restricted. Search Console offers Owner, Full, and Restricted. Owner has full control, including adding and removing other users. Restricted has simple view rights on most data, which is all an auditor needs.

Search Console, Settings > Users and permissions. The Restricted role gives read-only view rights, which is all an audit needs. Interface shown as of June 2026.

Restricted users cannot change settings, cannot submit or remove sitemaps, cannot request removals, and cannot touch other users. They can look, and that is the point. When the audit is finished, open the same screen and remove the user.

GA4: the Viewer role

If you want to share Analytics, go to Admin > Property Access Management, add the email, and choose Viewer. GA4 has Administrator, Editor, Marketer, Analyst, and Viewer. Viewer is the read-only floor: it can see report data and settings and build explorations, but it cannot change configuration or manage users.

GA4, Admin > Property Access Management. The Viewer role is read-only: see reports and settings, change nothing. Interface shown as of June 2026.

Prefer not to share access at all? A good audit can still run on exports and screenshots: your Search Console performance, coverage, and a few key reports. It is slightly less thorough than live access, but it keeps you fully in control of what is shared.

What you should never hand over for an audit

If someone needs any of the following just to tell you what is wrong with your site, the request does not match the job. None of these are required to read your data and write a fix list.

Your website admin or CMS password. A login to WordPress, Shopify, or your CMS lets someone change the site, not just read it. An audit changes nothing.
Hosting or cPanel access. Server-level access controls files, databases, and email. There is no audit reason to hold it.
Domain registrar login. Whoever controls the registrar can move or lose the domain itself. Never share it for analysis.
Search Console Owner. Owner can add and remove users and change verification. Restricted is the correct level for an outside reviewer.
Anything financial. Ad accounts with payment methods, billing portals, or card details have nothing to do with an SEO diagnosis.

The pattern is simple. Reading your data needs a read-only role on the data. Anything that can change, move, charge, or delete is not part of finding out what is wrong.

The "no access, no service" red flag

Some providers will not start until they have full back-end access to your site. It is often written into the terms: without admin access, the service cannot be delivered. For an ongoing engagement that implements changes every month, that is at least understandable. For an audit, it is the wrong shape entirely.

Demanding full control before anyone has even told you what is broken inverts the order. You are handing over the keys to buy a diagnosis. A diagnosis comes first, from reading the data, and only then does the question of who changes what, with how much access, even arise. If the only access on offer is all of it, that tells you the product is a retainer, not an audit. (For more on how those retainers are structured, see what a typical SEO retainer actually does.)

Access is also a provider-selection test. The guide to choosing an SEO agency in the Philippines shows how to compare permission requests alongside evidence, deliverables, ownership, reporting, and contract terms.

When backend access is legitimate

There is a real case for deeper access, and it is worth stating clearly so this does not read as if access is always suspect. Once you have the audit and decide to have the fixes implemented, editing the site obviously requires the ability to edit the site.

The difference is that implementation is a separate step, under a separate agreement, with a separate and scoped level of access, granted only for the work being done and removed afterward. That is the opposite of handing over admin up front as a condition of starting. Implementation may require write access; the audit never does. Keeping those two things apart is what keeps you in control.

Access closeout checklist

Use a named individual account instead of sharing a password.
Keep the business-controlled account as the property owner.
Record the role, purpose, approver, and intended removal date.
Grant implementation access under a separate scope, only after the proposed change is approved.
Remove the auditor after delivery and confirm that no temporary verification token or implementation account remains.

The bottom line

An audit reads, it does not write. The honest version needs your URL, a Restricted user in Search Console, and optionally a Viewer in GA4. Everything beyond that is either convenience for the provider or a sign you are being sold something larger than a diagnosis. Grant the viewing roles, keep the keys, and remove access when the work is done.

The fixed-price SEO audit works exactly this way: Restricted Search Console access (or your exports), a technical and on-page review of your site and search data, and a prioritized fix list you own. One report at a flat $150, no retainer, no admin login, no ranking promises. If you choose an ongoing retainer, any access needed to implement an approved fix is scoped separately. Get in touch to start.

Sources checked

Search Console permissions and GA4 roles were rechecked against Google's official documentation on August 2, 2026.

Originally published on FloxoLab.

Should Exact Search Matches Always Come First?

Fri, 30 Oct 2026 13:00:00 +0000

Cover: original AI-generated concept illustration with a fictional interface, not a working product screenshot.

Suppose a workspace has an archived project named Atlas and an active project named Atlas North. Someone types "Atlas" into search. Should the exact title win, or should the project they opened yesterday appear first?

Both orders have a reasonable explanation. The awkward part is making the ranking understandable when the user expected the other one.

A possible compromise is an exact-match section above the broader results, with status and workspace visible on every row. That adds structure, but it also gives an archived item extra prominence. A simple relevance list is quieter, yet can make a precise query feel ignored.

Would you treat a project name differently from an identifier such as TASK-184? And would you expose an "exact matches only" control, or expect people to learn a query syntax?

How would you balance those choices in a search box used by both occasional visitors and people navigating dozens of times a day?

How to Read Your Monthly SEO Report (Results vs Activity) | FloxoLab

Wed, 28 Oct 2026 15:50:00 +0000

Direct answer: A useful monthly SEO report should show what changed for relevant pages and queries, whether that movement produced qualified clicks or business outcomes, why the change matters, and what happens next. If it only lists completed tasks or a sitewide visibility score, it is an activity log, not evidence of SEO progress.

Once a month a report lands in your inbox. It is well designed and full of numbers. It mentions keywords monitored, rankings tracked, and strategy adjusted. You skim it, see that work clearly happened, and pay the next invoice. The trouble is that almost none of it tells you the only thing you actually care about: are more of the right people finding your business through search than last month.

There is a name for the difference. An activity report tells you what was done. A results report tells you what changed. The two are easy to confuse because activity is visible and reassuring, while results are quiet and sometimes uncomfortable. The good news is that you can check the results yourself, in about ten minutes, from the same data your provider is reading. Here is how.

A ten-minute reading order

Read this	What a useful report should show	Warning sign
Comparison	Equal periods plus a longer view for seasonality	One isolated month with no baseline
Query and page fit	Relevant non-brand query families mapped to the pages meant to rank	A sitewide score or a list of unrelated ranking gains
Outcome ladder	Visibility, clicks, and qualified business outcomes kept distinct	Impressions, calls, leads, and sales blended into one success claim
Accountability	The shipped change, observable effect, next action, and owner	A task list with no result or decision attached

The one question a report should answer

A good SEO report opens with a plain summary a non-technical owner can read in two minutes: what happened, why it happened, and what comes next. If the first page is a wall of tasks ("monitored rankings, optimized meta tags, built citations") with no statement of whether search traffic went up or down, that is the first signal you are reading activity, not results.

Everything below is about getting to the real answer. You do not need the report to do it. You need Google Search Console, which is free, which is yours, and which holds the actual record of how your site performs in Google. If you are not sure you have access to it, that is worth fixing before anything else, because it is the scoreboard for the entire game.

Read the four numbers together

Open Search Console and go to the Performance report. Start with two equal periods, such as the latest 28 days versus the previous 28 days, then use a three-month or year-over-year view to check whether the movement is a trend or seasonality. The four headline metrics are useful only when you read them by page and query, not as four isolated sitewide scores.

A real three-month Performance report from a small business site (domain redacted). The four tiles are the headline: clicks, impressions, CTR, and average position. Search Console, June 2026.

Metric	What it can tell you	What to check beside it
Impressions	Google has started showing a page for one or more queries	Query relevance, page, position, and whether the growth is new or seasonal
Average position	Visibility is moving closer to or farther from the results people normally inspect	The exact query and page; a sitewide average mixes unrelated searches
Clicks	Some searchers chose the result and reached the site	Brand versus non-brand, query intent, and sample size
CTR	The share of impressions that became clicks	Position, result type, query mix, and whether a few clicks dominate a small total

For the established site in this example, 12,200 impressions show that Google already understands the commercial topics. The non-brand queries remain around positions 30 to 70, so the immediate problem is weak ranking rather than discovery. That diagnosis would be different for a page published last week, where the first relevant impressions at position 60 can be the beginning of normal testing.

When impressions matter before clicks

Impressions are an early visibility signal, not a sale. They matter when a new or substantially updated page begins appearing for the intended queries, then gains more relevant variants or moves from distant positions toward the first two pages. Google itself recommends watching trends in impressions and clicks rather than relying on position alone.

Healthy early signal: a new page starts receiving impressions for the intended topic, even at positions 40 to 80.
Measurable progress: the same relevant queries move from position 60 toward 30, then toward 20.
Work still required: a mature commercial page remains around position 35 for months and produces no qualified visits.
Possible misalignment: impressions rise mainly on queries the page does not actually answer.

At very low volume, clicks and CTR are noisy. A few brand searches, manual tests, or clicks from the owner can move the total sharply. Use them, but do not let three or four clicks overrule a much larger pattern in relevant impressions and query-level position.

Clicks can also undercount value when a search result answers an informational question or a local profile triggers a call, direction request, or booking before the website loads. The zero-click search measurement guide keeps those surface actions, AI citations, website visits, and qualified leads in separate evidence layers instead of redefining every impression as a result.

The same site's top queries. The two redacted rows at the top are brand searches; everything below is non-brand and earns zero clicks from page four and beyond. Search Console, June 2026.

Look down the list. "Vehicle graphics" was shown 1,020 times and got zero clicks at position 33.7. "Business cards" and "business card" together drew over a thousand impressions around position 50. "Business stationery" sat at position 72 with 252 impressions. These are relevant commercial searches, so the impressions prove query fit and demand. The positions explain why that visibility has not yet become visits.

Now look at the two redacted rows at the very top, the only rows with real clicks. Those are brand searches, people typing the company name. They sit at position 2.3 and 6.2, page one, with click-through rates of 14.7% and 11.2%. That contrast is the entire lesson on one screen. When the site reaches page one, people click at a healthy rate. Everywhere it does not, the clicks vanish. The site is not failing to attract interest. It is failing to rank where the interest already is.

Vanity traffic versus commercial intent

Not all traffic is equal, and this is where a report can flatter a number that does not matter. It is easy to win clicks on low-competition informational searches that never lead to a sale, then present the click count as a result. Look at the kind of query, not just the size of the number.

Commercial intent. Someone searching "vehicle graphics" or "business cards" is close to buying. A click here can become a customer. These are the queries that should be winning, and on this site they are the ones losing.
Vanity or off-target. A query like "video spokesperson", shown 123 times here with no clicks, may not even match what the business does. Ranking for it would add traffic that never converts. More visitors, no more customers.

The test is simple. For each query bringing meaningful traffic, ask whether that searcher could plausibly become a paying customer. If a report leans on total sessions or total impressions without ever separating buyer queries from filler, it is counting motion, not money.

The phrases that quietly mean nothing

Activity reports lean on a handful of phrases that sound like progress and commit to none. None of these are necessarily dishonest, but on their own, with no number attached, they describe effort, not outcome.

"We monitored your rankings." Watching is not moving. The question is whether the rankings improved, on which commercial queries, and by how much.
"We are adjusting the strategy." Fine, but to what, away from what, and what measurable change is it meant to produce by when.
"Your visibility increased." Ask which pages and queries gained impressions, how their positions changed, and whether the searches match the business. Relevant growth is a leading signal; an unexplained sitewide total is not enough.
"We optimized on-page elements and built citations." Tasks completed. Set them next to clicks and positions on money queries, or they are just a to-do list.

The fix is not to demand jargon. It is to ask one calm question of every line: what number moved because of this, and can I see it in Search Console? If the answer is missing month after month, the engagement is producing activity and reporting it as results. (For how those monthly engagements are priced and scoped, see what a typical SEO retainer actually does.)

What a real result looks like

Knowing what is hollow makes the real thing easy to recognize. A results report points at movement you can verify yourself:

Relevant impressions expanding. New or improved pages appear for the questions they were built to answer, not just loosely related terms.
Query-level position improving. A useful page climbing from position 60 toward 30, then toward the first two pages, is measurable progress before traffic becomes meaningful.
Clicks rising once visibility is competitive. Separate commercial and non-brand searches from brand traffic, tests, and unrelated informational clicks.
CTR improving at comparable positions. Do not compare CTR across completely different query mixes or ranking ranges.
Conversions from organic, where you track them. The end of the chain: clicks that became enquiries, calls, or sales.

Each of these is a number you can pull up in your own Search Console, with a before and an after. That is the difference. A result survives you checking it.

This is your data

The quiet point under all of this is ownership. Search Console belongs to you, not to whoever does your SEO. The whole scoreboard, every click, impression, query, and position, is yours to read whenever you like. A provider reading it for you is fine. A provider standing between you and it is not. You should always keep your own access, which is also why an outside reviewer only ever needs read-only access to look, never the keys to your site. (More on that in what access an SEO audit actually needs.)

The bottom line

A monthly report should show whether the right search visibility is developing and whether it is turning into useful visits over time. Compare equal periods, open the Pages and Queries tabs, and follow the sequence: relevant impressions, improving positions, clicks, then qualified outcomes. Treat "monitored", "adjusting", and "visibility" as prompts for evidence, not as evidence by themselves.

Common questions about reading an SEO report

How often should you read your SEO report?

Once a month is enough to act on. Compare the latest period with an equal previous period, then check a three-month or year-over-year view for seasonality. New pages can be reviewed by impressions, query fit, and position before they have enough clicks to evaluate.

What should a good SEO report include?

A plain two-minute summary first: what changed, where it changed, why it may have changed, and what happens next. Then impressions, position, clicks, and CTR broken down by the pages and queries that matter, with brand, irrelevant queries, and low-volume noise identified separately.

What is a good click through rate and average position?

There is no universal good CTR or position. Search appearance, device, brand familiarity, intent, and the result layout all change the numbers. Track the same page and query group over time. For a new page, relevant impressions and movement from distant positions are useful early signals; evaluate CTR only after the page receives enough comparable impressions.

Is an SEO report the same as an SEO audit?

No. A report is the recurring scoreboard, read monthly to see whether traffic is moving. An audit is a one time diagnosis of why it is or is not, a technical and on-page review that ends in a prioritized fix list. You read a report yourself in about ten minutes; an SEO audit is the deeper look behind it.

Want to know why your commercial queries are stuck on page four instead of page one? That is exactly what the fixed-price SEO audit answers: a technical and on-page review of your site and your real Search Console data, with a prioritized fix list you own. One report at a flat $150, no retainer, no ranking promises. Want that monthly report and the fixes behind it done for you, not just explained? That is what an ongoing monthly retainer is for. Get in touch to start.

Sources checked

Search Console metric definitions and comparison guidance were rechecked against Google's official documentation on August 2, 2026.

Originally published on FloxoLab.

What to Check in Search Console Before You Pay for SEO | FloxoLab

Tue, 27 Oct 2026 15:50:00 +0000

Direct answer: Before paying for SEO, use Search Console to check three things: whether relevant pages earn impressions and clicks, whether the queries match real customers, and whether Google's canonical versions of your important pages are indexed. The result tells you whether to keep monitoring, request a diagnosis, or fix access and indexing first. It does not identify every underlying cause.

The pitch for SEO usually arrives before any look at your actual data. Someone offers a monthly retainer, or an audit, and the case for it is made in general terms: rankings, visibility, growth. What is almost never said is that you can do a meaningful first pass yourself, for nothing, in the same tool the professionals open first. Doing it changes the conversation. You stop buying SEO on faith and start buying it against numbers you have already seen.

This guide is a short, honest pre-audit. Three checks, all in Google Search Console, each pointing at a different part of the picture: are you getting traffic, is it the right traffic, and are your pages even in Google at all. None of it requires a login to anything but your own account, and none of it tells you how to fix what you find. That part is a real audit. The point here is to decide whether paying for one is worth it, and to walk in knowing what you are looking at.

If you are not sure you have Search Console access, fix that first. It is free to set up, it belongs to you, and an outside reviewer only ever needs read-only access to read it. (More on that in what access an SEO audit actually needs.)

Quick pre-audit decision map

What you see	What it suggests	Next move
Relevant queries and pages are growing, and key pages are indexed	The current work may be progressing normally	Keep the comparison consistent and monitor qualified outcomes
Relevant impressions exist, but clicks are scarce and positions remain distant	Demand exists, but the result is not competitive or well matched yet	Diagnose the affected queries and landing pages before buying a broad package
Growth comes from irrelevant queries	The total hides a topic or intent mismatch	Refocus the pages and reporting on commercial query families
An important canonical URL is missing from Google	Indexability, canonicalization, discovery, or quality needs investigation	Inspect that exact URL and its linked canonical before proposing a fix
Duplicates, redirects, 404s, or intentional noindex pages are excluded	The exclusion may be expected	Confirm intent. Do not treat every non-indexed URL as an error.

Check 1: The four numbers that say whether anything is working

Open the Performance report and set the date range to the last three months. A single month swings with seasons and holidays, so a trend tells you far more than a snapshot. At the top sit four tiles. These four numbers are the whole headline.

If you are deciding whether a campaign simply needs time, use the SEO progress checkpoint framework to separate a change that has not been shipped, a crawl or indexing problem, early impressions, useful clicks, and actual leads.

A real three-month Performance report from a small business site (domain redacted). Clicks, impressions, CTR, and average position. Search Console, June 2026.

Clicks count visits from Google Search. They are a surface action, not a lead or sale, and should be compared with the queries and pages that produced them.
Impressions count how often a result from the site appeared. Here, 12,200 impressions show that Google is already testing or ranking pages for a meaningful set of searches.
CTR is the share of impressions that became clicks. A 0.6% sitewide CTR needs query, page, position, device, and result-type context before it means anything actionable.
Average position summarizes the top position recorded for the site's result across many impressions. An average of 36.6 suggests distant visibility, but it is not a literal page-four rank for every query.

Read together, the four numbers describe the symptom in one line: the site has visibility, but much of it is too distant or poorly matched to earn clicks. They do not identify the cause. The next diagnosis should test query intent, landing-page usefulness, titles, competition, authority, and technical barriers before anyone sells a fix. If you want the longer read on telling a real result from busywork, that is the whole of how to read your monthly SEO report.

This diagnosis is specific to commercial pages stranded around page four. Local profiles and answer surfaces can sometimes produce calls, directions, bookings, or citations without a website visit. Use the zero-click measurement scorecard to record those outcomes separately, while keeping impressions, clicks, and qualified business results distinct.

If this comparison becomes a recurring weekly task, use the safe SEO automation with n8n workflow to prepare the evidence and route a review queue. Keep titles, canonicals, redirects, indexing controls, and published copy behind a person.

Check 2: Whether the traffic is the right traffic

Total numbers hide the thing that matters most, which is intent. Switch to the Queries tab. It lists the actual search terms people used, and it is where you tell buyer traffic from filler.

The same site's top queries. The two redacted rows at the top are brand searches and carry every click; the commercial terms below earn none. Search Console, June 2026.

On this site the only rows with real clicks are brand searches, people typing the company name, sitting on page one with healthy click-through rates. Everything below is non-brand. "Vehicle graphics" was shown over a thousand times and got zero clicks from page four. "Business cards" drew more than a thousand impressions, again no clicks, stuck around page five. These are real commercial searches by people who want to buy what the business sells, and not one converted into a visit.

Search Console now offers a branded-query filter for eligible properties, but the first-page result mix needs a separate inspection. Use the brand SERP audit to connect branded query data with the official website, Business Profile or knowledge panel, social profiles, reviews, entity consistency, and unwanted results.

That contrast is the test you run yourself. For each query bringing real impressions, ask two things: could this searcher plausibly become a customer, and where do we rank for it. Commercial terms with impressions and no clicks, sitting on page three or worse, are opportunity sitting on the table. Filler terms that would never convert are not worth chasing no matter how many impressions they show. If two URLs appear for the same valuable query, use the Search Console cannibalization check before assuming they compete; different pages may serve different intent. If a future report leans on total impressions without separating buyer queries from filler, you will already know to push back.

Check 3: Whether your pages are even in Google

The first two checks assume Google has your pages to show. This one tests that assumption, and it is the check most owners never run. Open Indexing, then Pages. The top of the report shows two numbers: how many pages are indexed, and how many are not.

The Page indexing report from a real site (domain redacted): 730 pages indexed, 933 not indexed. The raw split looks alarming, but the reason behind it is what matters. Search Console, June 2026.

Here 730 pages are indexed and 933 are not. At first glance that looks like a disaster, more than half the known pages missing from Google. But "not indexed" is not automatically bad. Google says plainly not to expect every URL to be indexed, because plenty of URLs are never meant to be: redirects, thank-you pages, filtered duplicates, anything you marked noindex on purpose. To know whether this is a problem, you have to open the breakdown.

The same site's "Why pages aren't indexed" table. Two rows tell the real story: 557 pages crawled and not indexed, and 115 discovered and not crawled. Search Console, June 2026.

Scroll the "Why pages aren't indexed" table and sort the reasons into two groups. The first is ordinary housekeeping. Page with redirect (162), Not found 404 (47), Soft 404 (10), Alternate page with proper canonical tag (5), Excluded by noindex (1), Blocked by robots.txt (1). On most sites this is normal background noise, the natural residue of moving pages around and keeping junk out of the index. None of it should keep you up at night.

The second group is the one that matters, and on this site it is enormous. Crawled, currently not indexed: 557. Discovered, currently not indexed: 115. Together that is 672 pages, far more than the housekeeping rows combined. These two statuses mean something specific. "Crawled, currently not indexed" means Google fetched the page but did not index it. "Discovered, currently not indexed" means Google knows the URL exists but has not crawled it yet. The counts are a signal to sample the actual URLs, not proof of one sitewide cause. Use the full Crawled - currently not indexed diagnosis to separate technical conflicts, duplicate intent, weak pages, and URLs that never needed indexing.

That is the real diagnosis, and it lines up exactly with Checks 1 and 2. A site whose pages mostly sit unindexed or buried on page four does not have a visibility problem that more "optimization" will solve by itself. It has a quality and structure problem that a competent audit should name. To sanity-check it on your own pages, paste a few of your important URLs into URL Inspection at the top of Search Console and confirm they actually say "URL is on Google". If your money pages are not, you have found something worth paying to fix.

Red flags that mean yes, get eyes on it

Put the three checks together. If you see several of these, a one-time audit will almost certainly pay for itself by telling you what to fix first:

Commercial queries stuck on page three or worse, with impressions but almost no clicks. The demand exists and you are not capturing it.
Important pages not indexed, especially showing up under "Crawled, currently not indexed". Google has seen them and passed.
Indexed count far below the number of real pages you publish. If you have 200 service and product pages and 40 are indexed, something structural is wrong.
Impressions climbing while clicks stay flat. The classic "visibility went up" story that produces no business.
CTR near zero on terms you should own. Appearing without being chosen is its own problem.

Green flags that mean you are probably fine for now

The honest version of this guide has to include the other outcome. Sometimes the pre-audit tells you to keep your money:

Clicks rising on commercial queries quarter over quarter, not just impressions.
Money pages indexed and ranking on page one or two for terms with real intent.
A not-indexed bucket that is mostly housekeeping, redirects and 404s and intentional noindex, with few surprises in "Crawled, currently not indexed".
Healthy CTR on the searches that matter, in the range your brand terms already get.

If that is your picture, you do not need to hire anyone this quarter. Keep reading your own data and revisit it in a few months. A provider who looks at this and still pushes a retainer is selling activity, not results.

What a pre-audit cannot tell you

This is where the free check ends and a paid one begins. Search Console shows you the symptoms clearly. It does not show you the cause. It will tell you that your commercial pages sit on page four, but not whether the reason is duplicated titles across a template, a canonical tag pointing the whole section at your homepage, parameter URLs eating your crawl budget, or thin content that genuinely deserves to rank lower. Those live in your code and your templates, where the dashboard cannot see, and several of them are exactly the technical fixes a dashboard-only agency will not touch.

A real audit takes what you found here, crawls the site to find the cause, and hands back a prioritized list of what to fix and in what order. It is also the context for judging an ongoing engagement: if you already pay a retainer, this pre-audit is a fair way to ask which of these numbers it has moved. For what those monthly engagements usually cover, see what a typical SEO retainer actually does.

The bottom line

Fifteen minutes in your own Search Console answers the only question that matters before you spend anything: is there a real problem here, and is it worth paying to solve. Read the four Performance tiles, check whether your commercial queries earn clicks, and open the Page indexing report to see whether Google is keeping your pages or quietly passing on them. If the picture is healthy, keep your money. If it is not, you now know precisely what to ask an audit to explain, and you will recognise a real answer when you get one.

Ran the checks and did not like what you saw? That is exactly what the fixed-price SEO audit turns into a plan: a full crawl plus your real Search Console data, with the causes named and a prioritized fix list you own. One report at a flat $150, no retainer, no ranking promises. And if the checks turn up recurring problems worth maintaining, a monthly SEO retainer keeps them in check. Get in touch to start.

Sources checked

Search Console Performance and Page indexing behavior were rechecked against Google's official documentation on August 2, 2026.

Google Search Console Help: the Page indexing report (index

Multilingual Recipe Search

Wed, 21 Oct 2026 19:31:41 +0000

When building Recipe Finder, we hit a frustrating limitation with our upstream data provider: the Spoonacular API only understands English queries.

If a user typed a craving in their native language—like cartofi in Romanian or стейк in Cyrillic—the search returned zero results, even when hundreds of matching recipes existed in the database. Worse, our search fallback logic would spend up to four API requests trying to find matches before giving up and rendering an empty state.

Rebuilding the entire platform around a new recipe database wasn't practical. Instead, for Release 2.20.0, we built a lightweight, fail-safe translation layer in front of the search pipeline using Google Gemini Flash and a normalized lookup cache.

What's New

Until now, Recipe Finder searched in English only. With release 2.20.0, the search automatically detects which language you wrote in and finds the exact same recipes you would get by searching in English:

Search in the language you think in, with no need to translate first.
Full support for non-Latin alphabets (e.g., Cyrillic queries return steak recipes, and searching for cartofi in Romanian returns potato recipes).
Zero impact on English queries, which behave identically to before.

How It Works: The Architecture

The core rule is deliberately simple: if a query is in English, we use exactly what you typed; if it isn't, we resolve its English translation before hitting the recipe API.

                [ Raw Query: "cartofi" ]
                            │
                            ▼
              ┌───────────────────────────┐
              │ Normalize (case & spaces) │
              └─────────────┬─────────────┘
                            │
                            ▼
                     ┌─────────────┐
           ┌─────────┤  DB Cache   ├─────────┐
           │         └─────────────┘         │
      MISS │                                 │ HIT
           ▼                                 │
 ┌───────────────────┐                       │
 │ Gemini Flash API  │                       │
 │ (Reasoning: Off)  │                       │
 └───┬───────────┬───┘                       │
     │           │                           │
   OK│           │ERROR / SLOW               │
     ▼           │(Fallback: raw query)      │
┌─────────┐      │                           │
│ Save DB │      │                           │
└────┬────┘      │                           │
     │           │                           │
     └───────────┴──────────┬────────────────┘
                            │
                            ▼
                [ Resolved: "potatoes" ]
                            │
                            ▼
              ┌───────────────────────────┐
              │  Spoonacular Search API   │
              │  & Relevance Re-Ranking   │
              └───────────────────────────┘

Step-by-Step Pipeline

Cache first: The incoming query is normalized (case and spacing) and looked up in our database. If we have seen it before, we already know the answer and skip the AI layer entirely.
One language check: On a first-time query, a single request to Google Gemini Flash decides whether the text is English and, if not, returns the English equivalent. Both outcomes are saved to the database—including "this is already English"—so common English searches never trigger a second check.
Search and rank with the right query: The recipe search runs with the resolved query, and results are ranked against it so the best matches appear first.
Safe by design: If the language check is slow, fails, or the database is unavailable, the search simply runs with the original query, exactly as it did before this release. Translation can never break a search.

Key Engineering Trade-offs

1. Sequential vs. Parallel Execution

We chose to run the language check before the recipe search, rather than in parallel. Running both at once would hide the wait on uncached queries, but it would also spend a recipe-search request on every non-English query—and that daily API quota is our scarcer resource.

2. Disabling Extended Reasoning

We disabled Gemini's extended reasoning for this specific request. Detecting and translating a short food phrase doesn't need chain-of-thought tokens, and leaving it off keeps the call significantly faster and cheaper. Other AI features in the app remain unaffected.

Performance and Cost

Speed: In our testing, first-time searches completed in roughly 1 to 1.5 seconds end-to-end, including the recipe search itself. Repeat searches hit the cache and skip the language check entirely.
Cost: Based on Google's published Gemini Flash pricing, we estimate roughly $0.0001 per language check, which works out to about $1 for every 10,000 new, distinct searches. Repeated searches cost nothing because of the cache.
Fewer wasted requests: A non-English search used to consume up to four recipe-search requests and still find nothing. It now uses one.

Current Limitations & What's Next

Recipe titles and descriptions are still shown in English, because that is how the recipes are stored upstream.
The results page currently displays what you typed rather than its translated equivalent.
The ingredient include/exclude filters are not translated yet.
The first search for a brand-new phrase takes slightly longer than a repeat search.

Next, we plan to add a "Showing results for…" indicator so it's clear when a search was translated, and extend the same translation pipeline to the ingredient filters.

If there's a language or regional dish phrase that doesn't work well for you, we'd love to hear about it—give it a try at recipe-finder.org!

Free SEO Tools Every Small Business Should Use (2026) | FloxoLab

Tue, 20 Oct 2026 15:50:00 +0000

Affiliate disclosure. Every tool in the main list is free. I also link to SE Ranking, the paid tool I use, here and near the end. If you start a trial through either link, I may earn a commission at no extra cost to you.

Most of the data that matters in SEO is free, at least at the start. How your site performs in Google, what people search to find you, and whether your pages are even indexed, is available at no cost from the source. Paid tools add convenience and depth on top, but if you have not yet used the free ones fully, that is where to start. Here they are, in the order a small business should adopt them.

01 Google Search Console

If you use one SEO tool, use this. Search Console is Google telling you, for free, exactly how your site does in its results: the queries you appear for, your clicks, impressions, average position, and click-through rate, plus whether each page is indexed and any problems Google found crawling your site. Its Links report also provides a useful sample of referring sites, target pages, and anchor text. Use the small-business backlink audit to turn that export into a keep, ignore, investigate, or reclaim queue without treating it as a complete link database. No paid tool can match Search Console for its own first-party data. Set it up, verify your site, and read it monthly. The full method is in the guide on what to check in Search Console before you pay for SEO, and on how to read your monthly SEO report.

02 Choose website analytics deliberately

Search Console covers search discovery even when you install no client-side analytics. Add website analytics when you need to understand landing pages, navigation, forms, or other on-site outcomes. For a simple privacy-first view, Cloudflare Web Analytics is free and states that it does not collect or use visitors' personal data. FloxoLab uses this lighter approach alongside Search Console.

Use Google Analytics 4 when the business genuinely needs detailed events, funnels, attribution, or Google Ads integration. GA4 is free, but it is not a neutral copy-and-paste default. Review consent requirements, data controls, and the information your forms or URLs may expose before adding the tag. The right choice is the smallest measurement setup that answers the business question.

03 Google PageSpeed Insights

Speed is a ranking factor and a conversion factor, and PageSpeed Insights is the free, canonical way to measure it. Paste a URL and it scores your Core Web Vitals using both lab tests and real-world field data from Chrome users, with specific recommendations. The practical next step is the guide to fixing Core Web Vitals without chasing the score. One caveat: the same Core Web Vitals data also appears in Search Console's experience report and in most paid all-in-one tools, so you may already have it. PageSpeed is the place to go deep on a single slow page rather than a tool you need to check daily.

04 Google Keyword Planner

Built into Google Ads and free to use, Keyword Planner gives you search volume ranges and keyword ideas straight from Google. It is built for advertisers, so the volumes come in broad bands rather than exact numbers, and you need a Google Ads account to reach it. But for free first-pass keyword research, what people actually search and roughly how often, it is a solid starting point before you ever pay for a dedicated research tool.

05 Bing Webmaster Tools

Often overlooked, and free. Bing Webmaster Tools is the Search Console equivalent for Bing, which still drives real traffic and now feeds AI search results. Beyond the usual indexing and performance data, it includes a genuinely useful free keyword research feature. Setting it up takes minutes, and you get a second search engine's view of your site at no cost.

06 Google Trends

Google Trends shows relative search interest over time and by region. It will not give you absolute volumes, but it is free and excellent for two things: spotting whether a topic is rising or fading, and comparing seasonal demand, which matters for a local business deciding when to push a service. Use it to time content, not to size it.

07 Screaming Frog (free version)

For a technical check, the free version of the Screaming Frog SEO Spider crawls up to 500 URLs, which covers most small business sites. It finds broken links, redirect chains, duplicate titles, and canonical problems, the under-the-hood issues the tools above do not surface. It has a learning curve, so read the full Screaming Frog review first to know whether it fits you, but for a free technical crawl of a small site, it is the best option there is.

When free finally runs out

Free tools cover the large majority of small business SEO, and you should use them fully before paying for anything. They hit their limits in three places: tracking many keywords day by day, watching what competitors rank for, and auditing larger or multiple sites without doing it all by hand. That is the point where a paid all-in-one tool stops being a luxury and starts saving real hours.

There is also a useful middle step before a subscription. I ran the Mangools Free+ allowance through all five tools on this real site. It was strong enough for a focused keyword, SERP, backlink, and domain-research session, but the shared lookup limits and one-location rank tracker make it a test bench rather than a permanent operating system.

Outgrown the free tools? The paid all-in-one I use and recommend for small business is SE Ranking: rank tracking, research, audits, and reports, with a 14-day free trial, no card. Read the full SE Ranking review first. If Semrush is also on your shortlist, compare the current plans and included features in the SE Ranking vs Semrush pricing guide.

Try SE Ranking free for 14 days →

The bottom line

The essential free starting point is Search Console. Add privacy-first or detailed analytics only when you need on-site behavior, use PageSpeed Insights for page experience, Keyword Planner and Bing for demand, Trends for timing, and Screaming Frog for a small technical crawl. A business competing in the map pack should first understand which local SEO actions it can handle itself, then use the narrower guide to local SEO tools for the Philippines. Pay for an all-in-one platform only when competitor research, recurring rank tracking, or multi-site work saves more time than the subscription costs.

Common questions

What free SEO tools does a small business actually need?

Google Search Console is the essential starting point. Add PageSpeed Insights for page experience, Keyword Planner or Bing for demand, and the free Screaming Frog crawler for technical checks. Website analytics is optional for SEO itself; choose Cloudflare Web Analytics for a lighter privacy-first view or GA4 when detailed events and attribution justify the additional setup.

Can I do SEO with only free tools?

For a single small site, largely yes. Free tools cover search performance, indexing, page experience, demand research, analytics, and a small technical crawl. You outgrow free when you need recurring keyword tracking, competitor data, larger crawls, or reporting across several sites.

Is Google Search Console better than paid SEO tools?

For its own job, yes. Search Console shows your real Google data: actual clicks, impressions, queries, and indexing, straight from the source, which no paid tool can match for accuracy. Paid tools add things Search Console does not do, like daily rank tracking, competitor research, and keyword databases. The two are complementary, not rivals.

Not sure what your free-tool data is actually telling you, or which problems matter most? That is what the fixed-price SEO audit is for: I read your real numbers and crawl your site, then hand back a prioritized fix list, one report at a flat $150, no retainer. See all the tools I use on the SEO tools page, or the wider SEO overview. Get in touch to start.

Sources checked

Originally published on FloxoLab.

Best AI Keyword Research Tools to Find Low-Competition Search Terms

Mon, 19 Oct 2026 11:15:34 +0000

Finding keywords with low competition is one of the most practical ways to build organic search traffic without competing directly against established websites for every valuable query. For bloggers, affiliate marketers, small businesses, and SEO professionals, the goal is to identify search terms that match a website's expertise, attract the right audience, and offer a realistic opportunity to rank.

AI-powered keyword research tools make this process faster. They help marketers discover related queries, group keywords by topic, examine search intent, analyze competing pages, and identify content opportunities that might otherwise go unnoticed. However, artificial intelligence does not automatically make a keyword easy to rank for. Reliable decisions still depend on search data, the quality of competing pages, website authority, and the usefulness of the content being published.

The best approach is to combine AI-assisted discovery with measurable SEO data. Here are the tools worth considering and how to use them to find low-competition search terms.

What Are Low-Competition Keywords?
Low-competition keywords are search terms for which a website has a reasonable opportunity to rank compared with the pages already appearing in search results.

These terms often have more specific wording than broad keywords. For example, a broad query such as "email marketing" covers a large subject and attracts competition from established software companies, publishers, and marketing agencies. A more specific query such as "email marketing automation for independent online stores" targets a narrower audience and a clearer need.

The longer query is not automatically easier to rank for. Its actual competition depends on the websites appearing in search results, the quality of their pages, the searcher's intent, and the amount of useful information available on the subject.

Low competition also does not necessarily mean high traffic. A keyword may be relatively easy to target but attract very few searches. Successful keyword research balances ranking opportunities with relevance, demand, and business value.

Why Use AI for Keyword Research?
Traditional keyword research often involves collecting search terms, checking their metrics, examining search results, and organizing the findings manually. AI-assisted tools can reduce the time required for several of these tasks.

They can help marketers:

Generate keyword ideas from a seed topic, product, or customer problem.

Discover related questions and longer, more specific search queries.

Group keywords into topical clusters for blog posts and landing pages.

Identify search intent and distinguish informational queries from commercial searches.

Compare keyword opportunities against competing pages.

Develop content briefs, article outlines, and related subtopics.

Find gaps between the subjects a website covers and the subjects its audience searches for.

The distinction between generating ideas and validating them is important. An AI system can suggest hundreds of plausible keywords, but suggestions alone do not establish search volume, ranking difficulty, or commercial value. Those details require suitable keyword data and direct examination of search results.

Best AI Keyword Research Tools to Consider

Semrush
Semrush is an established SEO platform that offers keyword research, competitor analysis, position tracking, and content optimization features. Its keyword research tools can help marketers evaluate search demand, keyword difficulty, and related terms before deciding which topics deserve attention.

For low-competition research, begin with a broad seed keyword connected to the website's subject. Review related terms, question-based queries, and more specific variations. Filter the results by relevant difficulty metrics, then investigate the search results for the strongest candidates.

Semrush is particularly useful when keyword research needs to connect with competitor analysis and a wider SEO workflow. A marketer can use it to identify topics competitors target and investigate areas where their own website has limited coverage.

Best for: SEO professionals, agencies, affiliate marketers, and businesses managing several content campaigns.

Important consideration: Keyword difficulty is a comparative estimate, not a guarantee of ranking success. Check the actual search results and the strength of the competing pages before committing to a topic.

Ahrefs
Ahrefs provides keyword research and competitor analysis tools that help marketers examine search demand, related queries, ranking pages, and backlink profiles.

Its keyword research workflow can reveal long-tail variations that are more specific than a primary keyword. These variations may help publishers find topics that larger websites have not covered adequately.

One useful method is to examine pages ranking for a broad subject and identify the related queries they address. Next, investigate narrower terms that match the website's audience. Review the competing pages and determine whether an original, more useful resource could answer the query better.

Ahrefs is also useful for examining backlinks to competing pages. Links can influence ranking performance, so understanding the link profiles of ranking pages provides additional context when evaluating a keyword opportunity.

Best for: Content publishers, link-building teams, affiliate websites, and SEO professionals conducting detailed competitor research.

Important consideration: A low keyword difficulty score does not eliminate the need for useful content, appropriate technical SEO, or relevant links where competition makes them important.

Google Keyword Planner
Google Keyword Planner is a keyword research tool designed primarily for planning Google Ads campaigns. It can also help organic search marketers discover keyword ideas and examine search-demand estimates.

The tool is useful for generating ideas from products, services, and existing website content. Marketers can investigate related terms and compare estimated demand across different keyword groups.

One distinction matters here: Google Ads competition measures advertiser competition, not organic search difficulty. A keyword marked as having low advertising competition may still be difficult to rank for in unpaid search results.

Use Keyword Planner to investigate demand and discover ideas, then evaluate organic competition separately by reviewing search results and, where appropriate, using an SEO platform.

Best for: Beginners, small businesses, and marketers who need a source of keyword ideas and advertising demand estimates.

Important consideration: Do not use the advertising competition column as a substitute for organic keyword difficulty.

Google Trends
Google Trends helps users compare the relative popularity of search terms over time and across geographic areas. It is particularly useful for identifying seasonal topics, emerging interests, and changes in search behavior.

For example, a publisher planning content about tax software, holiday marketing, or educational products can use Trends to investigate when interest typically increases. This information helps with editorial planning and can reveal opportunities to publish before demand peaks.

Google Trends does not provide a direct organic keyword difficulty score. Instead, it complements other tools by helping marketers understand whether a topic has sustained interest, seasonal demand, or signs of growing popularity.

Best for: Publishers covering seasonal subjects, news-related topics, consumer trends, and changing market interests.

Important consideration: Relative search interest is not the same as absolute search volume. Validate demand and competition with additional data before selecting a target keyword.

LowFruits
LowFruits is a keyword research tool focused on identifying long-tail search opportunities and analyzing weaknesses among pages appearing in search results.

This approach is particularly relevant to smaller websites. Instead of targeting only broad keywords with established competition, marketers can investigate specific queries where the current results may include weaker or less relevant pages.

A practical workflow begins with a seed topic or keyword list. The tool helps identify opportunities worth investigating, after which the marketer should examine the pages ranking for each query. Look for unanswered questions, outdated information, limited topic coverage, and pages that do not directly satisfy the searcher's intent.

Best for: Niche websites, smaller publishers, affiliate marketers, and bloggers looking for specific topics to target.

Important consideration: A weak competitor does not guarantee a ranking opportunity. Search intent, content quality, and the overall strength of the remaining results still matter.

Keyword Insights
Keyword Insights focuses on keyword clustering and content planning. It helps marketers organize related search terms into groups that can inform individual articles, landing pages, and broader content strategies.

This is useful when AI-generated research produces a large list of similar keywords. Rather than creating a separate article for every variation, marketers can group terms that share the same intent and determine whether one comprehensive page can satisfy them.

For example, several queries about choosing an email autoresponder may belong to one commercial research topic. Publishing separate pages for nearly identical queries could create unnecessary duplication. Grouping related terms helps clarify the appropriate content structure.

Best for: SEO agencies, content strategists, publishers with large keyword lists, and teams planning content at scale.

Important consideration: Automated clustering should be reviewed against actual search results. Similar wording does not always indicate identical intent.

ChatGPT
ChatGPT can assist with the discovery and organization stages of keyword research. It can generate seed keywords, expand topics into long-tail variations, identify common customer questions, propose audience-specific queries, and organize research into useful categories.

For example, a marketer promoting email automation software could request keyword ideas for small online stores, independent consultants, or digital course creators. Each audience has different needs, which can produce more targeted research directions.

ChatGPT can also help classify a verified keyword list by search intent, draft content briefs, and suggest questions an article should answer.

However, generated suggestions should not be treated as verified search data. Unless supported by current keyword research data or another reliable source, a proposed keyword's search volume, ranking difficulty, and commercial value remain unconfirmed.

Best for: Brainstorming, audience research, keyword categorization, content briefs, and organizing findings from dedicated SEO tools.

Important consideration: Use ChatGPT alongside a keyword data provider and live search results. It is an assistant for research, not a replacement for validating keyword metrics.

How to Find Low-Competition Keywords With AI
Choosing a tool is only the beginning. A repeatable research process helps prevent marketers from wasting time on irrelevant queries or keywords they cannot realistically target.

Step 1: Start With a Specific Topic
Begin with a subject closely connected to the website's audience and commercial goals.

An email marketing company might start with "email automation." A finance publisher might investigate budgeting software. A blogger covering website growth might start with technical SEO or link building.

The seed topic should reflect what the website can explain accurately and what its audience needs.

Step 2: Generate Long-Tail Keyword Ideas
Use an AI assistant or keyword research platform to expand the seed topic into specific queries.

For email automation, possible research directions include:

Email automation for small online stores.

How to set up a welcome email sequence.

Email autoresponders for digital product sales.

How to automate abandoned-cart emails.

Email marketing software for independent creators.

These examples are research starting points, not verified claims about search volume or competition. Each candidate requires validation.

Step 3: Check Search Demand
Use a keyword research platform to examine available search-volume estimates and related terms. Consider the geographic market, language, and audience you intend to reach.

A keyword with very little demand may not justify a standalone article. However, a collection of related low-volume queries may support a useful page when they share the same search intent.

Do not select keywords solely because they have the largest reported search volume. Relevance and the value of the traffic matter just as much.

Step 4: Evaluate Organic Competition
Review the actual search results for each promising query.

Ask these questions:

Are the top results published by major websites with strong authority in the subject?

Do the ranking pages answer the question directly?

Is the information current and complete?

Are there important questions that the existing pages do not address?

Could your website produce a more useful resource for the intended audience?

SEO difficulty scores can narrow the list, but direct examination of the competing pages provides essential context.

Step 5: Confirm Search Intent
Determine what users expect to find when they enter the query.

Informational searches call for explanations, tutorials, and practical guides. Commercial investigation searches often require comparisons, reviews, and feature breakdowns. Transactional searches may require product pages, pricing information, or clear paths to purchase.

A page that targets the right keyword but fails to satisfy the expected intent may struggle to rank or convert visitors.

Step 6: Group Related Keywords
Use a clustering tool or AI assistant to group keywords by topic and intent. Decide which queries belong on the same page and which require separate resources.

This process helps establish a content plan without creating unnecessary duplicate articles.

A well-organized website can use a main guide to cover a broad subject and supporting articles to answer specific questions. Internal links can then connect those pages where they provide genuine value to readers.

Step 7: Prioritize Commercial Value
A low-competition keyword is more useful when the resulting traffic supports the website's objectives.

A software company may prioritize searches from people comparing tools or looking for a solution to a specific business problem. An educational publisher may focus on informational searches that attract its intended readership.

Evaluate each candidate by relevance, demand, likely ranking opportunity, search intent, and potential business value. Do not assume that every keyword with a low difficulty score deserves an article.

Step 8: Publish, Measure, and Improve
After publishing, monitor impressions, clicks, rankings, and relevant conversions using available analytics and search performance tools.

If a page receives impressions but few clicks, examine the title and description and compare them with the search intent. If it attracts visitors but produces little engagement or few conversions, review whether the content addresses the right audience and provides a useful next step.

Update pages when the subject, evidence, or user needs change. Use actual performance data to guide the next round of keyword research.

Common Mistakes to Avoid
Treating AI suggestions as verified data. Keyword ideas are not proof of search demand. Validate them with suitable tools.

Confusing paid and organic competition. Advertising competition and organic ranking difficulty measure different things.

Chasing low difficulty without checking relevance. A keyword is not valuable merely because it appears easy to target.

Creating a separate article for every variation. Closely related queries may belong on one comprehensive page.

Ignoring search intent. Content must answer the question or meet the need that prompted the search.

Overlooking the competition itself. Metrics cannot fully explain why particular pages rank. Examine the content, relevance, links, and overall quality of the results.

Which AI Keyword Research Tool Should You Choose?
The right choice depends on the research task and available budget.

Semrush and Ahrefs are useful options for broader SEO research and competitor analysis. Google Keyword Planner helps discover keywords and examine advertising demand, while Google Trends adds context about interest over time. LowFruits focuses on long-tail opportunities, and Keyword Insights supports clustering and content planning. ChatGPT can help generate ideas and organize findings, provided its suggestions are checked against reliable data.

For a beginner, a practical starting workflow is to generate ideas with ChatGPT, examine demand with Google's research tools, review the search results, and use a dedicated SEO platform when more detailed competition analysis is necessary.

For an established SEO team, combining keyword research, competitor analysis, clustering, and performance tracking can provide a more complete process.

Final Thoughts
Finding low-competition search terms requires more than asking an AI tool to produce a keyword list. The strongest opportunities come from combining relevant ideas with validated search data, careful analysis of existing results, and a clear understanding of the intended audience.

Start with specific customer problems. Expand them into long-tail queries. Check search demand, inspect competing pages, confirm search intent, and prioritize terms that support the website's goals.

AI can make the research process more efficient, but ranking decisions should remain grounded in evidence. The objective is not to publish the largest number of keyword-targeted articles. It is to publish useful pages for searches where the website has a credible opportunity to compete and deliver value to readers.

SE Ranking vs Semrush (2026): Pricing and Features Compared

Sat, 17 Oct 2026 15:50:00 +0000

Affiliate disclosure. This comparison links to SE Ranking here and near the end. If you start a trial or subscribe through either link, I may earn a commission at no extra cost to you. I use SE Ranking hands-on; the Semrush side uses published plans, official screenshots, and a limited free view. Prices were checked July 2026.

Quick verdict

Pick SE Ranking if

You are a small business, freelancer, or small agency. It is cheaper for SEO with AI included, starts with no credit card, and is simpler to learn. This is most people.

Pick Semrush if

You need the deepest backlink database, the most mature AI visibility data, or a full marketing suite across many clients. That depth is what agencies and larger teams pay for.

SE Ranking and Semrush have been compared for years as "the affordable one" and "the deep one." In 2026 that framing is still broadly right, but the details changed. Both now sell SEO and AI search visibility together, both split the price into a base plan plus add-ons, and the cheap headline number no longer tells you what you will actually pay. This page untangles that, then shows the same keyword, rank tracker, and audit in each tool so you can see the difference rather than take my word for it.

Why is this comparison so confusing in 2026?

Because neither tool has one price. Each sells in layers, and the entry number you see first is not the whole cost. Here is the mental model that makes it simple.

Semrush sells two lines. Semrush One bundles SEO and AI together (Starter $199, Pro+ $299, Advanced $549). SEO Classic is SEO only and cheaper (Pro $139.95, Guru $249.95, Business $499.95), with AI visibility sold as a separate toolkit on top.
SE Ranking puts SEO and a baseline of GEO into every plan (Core $129, Growth $279), then sells a heavier AI Search add-on from $89 a month for teams that go deep on AI visibility.

So the fair head-to-head for the tool most people buy is SE Ranking Core at $129 against Semrush One Starter at $199: both are the entry all-in-one SEO plus AI plan. Everything below compares those two, with the higher tiers noted where they matter. This page focuses on the AI-inclusive line; if you only want classic SEO, my hands-on SE Ranking review covers the SEO Classic price angle in more detail.

How do the prices really compare?

For an all-in-one SEO plus AI plan, SE Ranking is cheaper at the entry point and the two move closer together as you scale. Both vendors run discounts and change pricing, so treat this as a July 2026 snapshot and check the live pages before you buy.

Plan	Monthly	AI / GEO included?	Trial	Card to start?
SE Ranking Core	$129	Yes, baseline (100 prompts, 5 GEO domains)	14 days	No
SE Ranking Growth	$279	Yes (250 prompts, 15 GEO domains)	14 days	No
Semrush One Starter	$199	Yes, bundled (50 prompts, 1 AI domain)	7 days	Yes
Semrush One Pro+	$299	Yes (100 prompts)	7 days	Yes

Cheaper SEO-only path: Semrush SEO Classic Pro $139.95 (no AI). Heavier AI on SE Ranking: AI Search add-on from $89/mo. Annual billing saves roughly 20% on SE Ranking and 17% on Semrush.

The two checkout screens below make the entry difference concrete. SE Ranking started a full trial with no card and showed $0 estimated tax on my account. Semrush asked for a card before the trial, and the advertised $199 became a $222.88 first charge once tax was added.

SE Ranking Core checkout: $129, no card, $0 estimated tax on my account.

Semrush One Starter checkout: a card is required, and with tax the first charge comes to $222.88, above the $199 sticker price.

One caveat, so this stays fair: tax depends on your country. SE Ranking adds tax at checkout too, and mine simply came out to $0 here in the Philippines while Semrush added it. Check your own total. The difference that holds for everyone is the card: SE Ranking lets you start without one, Semrush does not.

Does SE Ranking include AI, or is it an add-on?

It is included. Every SE Ranking plan, Core included, comes with a baseline of AI and GEO tracking: around 100 prompts a day and five domains in GEO research. You do not need the add-on to start watching how you appear in AI search. The $89 AI Search add-on is for going deeper: many more prompts, unlimited AI competitor research, and the SE Visible dashboard for brand mentions, citations, and sentiment.

Semrush handles it differently. Semrush One bundles AI into the plan, so the cheapest AI-inclusive option is One Starter at $199. Its SEO Classic line does not include AI at all; you add that as a separate toolkit. So the summary is simple: SE Ranking folds a starter level of AI into every plan, while Semrush either bundles it at a higher base price or sells it separately. There is a fair counter-point, though: 100 prompts is a starter allowance, and anyone doing serious AI visibility work on either tool will pay more, which narrows the gap.

Same keyword, two tools: how different is the data?

This is the cleanest test, because it is the same keyword in both tools on the same day. I ran local seo philippines through each. The local search volume matched exactly, and the rest diverged in ways worth understanding.

SE Ranking: 210 local volume, difficulty 17/100, intent Local + Commercial.

Semrush: 210 local volume, difficulty 10%, intent Informational.

Metric	SE Ranking	Semrush
Local volume (PH)	210	210
Global volume	330	500
Difficulty	17 / 100 (Effortless)	10% (Very easy)
Search intent	Local + Commercial	Informational
CPC / competition	No CPC data, 0.01	$0, 0.01

The local volume being identical is reassuring: both read the core number the same way. The global volume differs because each vendor builds its own database from different clickstream and modeling, so a gap of a few hundred is normal, not a bug. The difficulty scores agree in spirit (both say this keyword is easy) even though the scales differ.

The intent label is the one to watch. SE Ranking calls this keyword Local plus Commercial; Semrush calls it Informational. Same keyword, two different verdicts, because each tool guesses intent with its own model. Treat the intent tag as a hint, not a ruling, and confirm it against the actual search results before you build a page around it. That single habit will save you from writing the wrong kind of content on a good keyword.

Rank tracking: how do the trackers compare?

Rank tracking is SE Ranking's heritage, and it shows in a clean daily list with location down to the city, SERP features, and a content score column. Semrush position tracking is capable too, though its dashboard leads with visibility and traffic estimates and takes a day to populate a new campaign.

SE Ranking rank tracking on my own site (floxolab.com, Philippines).

Semrush position tracking on a different site I manage (US target).

These two screens are different sites, so compare the interface, not the numbers. SE Ranking gives you the per-keyword detail first, which is what you want for local work. Semrush frames the same job around visibility share and estimated traffic, which suits a reporting or agency view. SE Ranking has been accurate in my daily use, and Semrush is a long-established tracker; for you the difference is what each one shows first.

AI visibility and GEO: what do you actually get?

This is the 2026 headline for both tools: tracking whether you appear in AI answers, not just in blue links. SE Ranking's tracker was live on my account, so here is real data. It shows AI Overviews appearing for my tracked prompts, and it does not hide the hard part: the overviews exist, but my site is not cited in them yet. That gap is exactly what the tool is for.

SE Ranking AI Overview tracker: overviews show for these queries, my site is not yet cited.

The prompt list you track, from "best SEO agency in the Philippines" to automation queries.

You pick prompts the way you would pick keywords, and the tracker reports whether AI answers mention you and whether they link you, day by day. Semrush offers the same idea through its AI Visibility toolkit, and its documentation describes an MCP connector that lets an AI assistant like ChatGPT or Claude pull live Semrush data into a conversation. I could not get past the card wall to test the Semrush tracker myself, so that detail comes from Semrush's own materials, and the screenshot below is only the trial gate I hit.

Semrush AI Visibility, gated behind a card-required trial: this is as far as I got.

Site audit: which crawler is more useful?

Both crawl your site and group issues by severity. The two screens below are different sites, so read them as interface, not scorecards. SE Ranking's audit is clean and quick to read: indexability, status codes, and issues split into notices, warnings, and errors. Semrush's audit is denser and goes further, and it has one genuinely forward-looking feature SE Ranking's does not: an AI Search Health score with checks for semantic HTML and whether AI crawlers like ChatGPT-User are blocked.

SE Ranking site audit (my site): clean layout, issues by severity.

Semrush site audit (a different site): denser, with an AI Search Health score.

If your priority is a fast, readable technical audit, SE Ranking gets you there with less noise. If you want the deepest issue coverage and the newer AI-readiness checks in one report, Semrush leads here, and that is a fair reason to pay more for it.

Which is easier to start with?

SE Ranking, on two counts. First, the no-card trial: you can set up a project and use the tool for 14 days before deciding, versus 7 days behind a card on Semrush. Second, the interface. Both are full suites with a lot in the sidebar, but SE Ranking surfaces the everyday tools (rank tracking, audit, research) more directly, while Semrush spreads its power across many toolkits that take longer to learn.

SE Ranking dashboard: one project, the core metrics up front.

Semrush home: more toolkits, more surface area to learn.

Where is Semrush genuinely stronger?

Price and ease are not the whole story, and it would be a poor comparison if it pretended Semrush had no edge. It has a real one, in three places.

Semrush leads on

Backlink database size: far more indexed backlinks and keywords, which matters for forensic link analysis and large-scale campaigns.
AI visibility maturity: a larger, longer-running dataset behind its AI search tracking, plus an MCP connector that feeds live data into AI assistants.
Breadth: a full marketing suite across PPC, social, content, and PR that goes well beyond core SEO.

SE Ranking leads on

Price for SEO with AI included, and a no-card 14-day trial.
Rank tracking depth and clarity, with city-level local targeting.
A simpler interface and white-label client reporting without enterprise pricing.

Crawled - Currently Not Indexed: What to Fix | FloxoLab

Tue, 06 Oct 2026 15:50:00 +0000

Google still defines Crawled - currently not indexed in the Page indexing report as a page that Google crawled but did not index. Google adds that the page may or may not be indexed later and that there is no need to resubmit the URL for crawling. The label confirms a crawl happened. It does not identify one universal defect, and it does not promise that a technically indexable page will be selected for the index.

The useful question is not "How do I clear this warning?" It is "What should happen to this specific URL?" An important service page, an expired campaign page, a duplicate product filter, and a thin archive should not receive the same treatment. Start with the intended outcome.

Choose the right outcome before changing the page

What you find	Best next action	Why
Unique, useful page with a technical or rendering conflict	Fix	Keep the URL and remove the evidence-backed obstacle
Page overlaps a stronger URL that serves the same intent	Consolidate	Merge useful material and use a permanent redirect when the old URL is retired
Useful to visitors but should not appear in search	Noindex	Keep it accessible while explicitly excluding it from search results
Temporary or recent URL with no conflicting signals	Leave it alone and monitor	Crawling and indexing are separate, and inclusion is not guaranteed on a fixed schedule
Obsolete page with no relevant replacement	Remove	Return a real 404 or 410 instead of preserving an empty 200 page

Do not bulk-request indexing first. Google says repeated requests for the same URL do not make crawling faster, and a crawl request does not guarantee inclusion. Use the request only after a meaningful fix or update.

Step 1: confirm the exact URL and current state

In Search Console, open Indexing → Pages → Crawled - currently not indexed, export the examples, and pick a small representative sample. Separate important pages from parameters, feeds, media URLs, old campaign paths, and other URLs that were never meant to rank. A large count can hide several unrelated patterns.

Paste one complete URL into URL Inspection. The indexed result reports what Google knows from its stored data, not necessarily what is live now. Record the last crawl time, crawl result, whether indexing was allowed, the user-declared canonical, and any referring page or sitemap information shown. Then run Test live URL if the page has changed or you suspect the stored crawl is stale.

The live test answers a narrower question: can Google fetch and process the current page? Google explicitly says it cannot predict indexing success, canonical selection, or the Crawled - currently not indexed state. A green "URL is available to Google" result is useful, but it is not proof that the URL will be indexed.

Step 2: check indexability and the response Google receives

For a page you want indexed, the live response should be a stable 200, accessible without a login, allowed by robots.txt, and free of a noindex rule in both the HTML and HTTP headers. Check the rendered HTML that URL Inspection received, not only the source your browser shows.

HTTP status: the intended page returns 200, not a redirect loop, intermittent 5xx, 403, or authentication response.
Robots access: Googlebot can crawl the page and the CSS, JavaScript, and other resources needed to render its main content.
Indexing directive: there is no accidental robots meta tag or X-Robots-Tag: noindex.
Rendered content: the screenshot and rendered HTML contain the main heading, body, links, and useful page-specific information.
Error content: the page is not a product-missing message, empty search result, or not-found template returning 200.

Robots.txt is not a reliable way to remove a web page from search. Google may still know and show a blocked URL, and a blocked crawler cannot see a noindex rule on the page. If the URL must stay public but out of search, allow crawling and use noindex. If it is private, require authentication.

Step 3: align canonical, sitemap, and redirect signals

Canonicalization happens during indexing, so the live test cannot tell you which canonical Google will choose. You can still remove obvious conflicts. A page meant to stand alone should normally have a self-referencing canonical. Its internal links, sitemap entry, redirects, and alternate versions should consistently point to the same preferred clean URL.

Check for common contradictions: the page declares another URL as canonical, the sitemap lists a parameter or HTTP version, internal links point through a redirect, or several near-identical URLs all declare themselves canonical. Google treats canonical annotations, redirects, sitemap inclusion, and other signals as inputs, not commands. Conflicting signals make the preferred version less clear.

A sitemap helps Google discover preferred URLs. It does not force Google to crawl or index them. Keep only canonical, indexable URLs in the sitemap, use accurate lastmod values when content actually changes, and do not resubmit the file as a substitute for fixing the page.

If the submitted file lists redirect sources or URLs that canonicalize elsewhere, use the sitemap redirect and canonical cleanup workflow to audit the final response, replace each obsolete entry, and repair the generator that keeps adding it.

Step 4: make sure the page is discoverable in context

Every important page should have at least one crawlable link from another page, and a business-critical page usually deserves several relevant paths. Use normal <a href="https://floxolab.com/seo/guides/..."> links with descriptive anchor text. Do not rely only on a sitemap, a JavaScript click handler, an orphaned card loaded after interaction, or a navigation search box.

Link from pages that naturally explain the relationship. A service page can link to the detailed guide that supports it. A related guide can point to the next troubleshooting step. This helps users navigate and gives Google clearer context about why the URL exists. For the broader site-level check, use the Search Console pre-audit to separate isolated URLs from a wider indexing pattern.

Step 5: decide whether the URL deserves its own result

Technical cleanliness is necessary, but it is not a guarantee of selection. Compare the page with the strongest page on your own site that answers the same search need. If both URLs would satisfy the same person with substantially the same answer, creating a second canonical page may not help anyone. When both URLs already earn impressions, use the keyword cannibalization workflow in Search Console to compare their query, intent, and performance before choosing a keeper.

Ask concrete questions instead of counting words:

Does the page solve a distinct user problem that no stronger page already solves?
Does it contain original evidence, examples, decisions, or first-hand detail beyond a generic summary?
Is the main answer complete without requiring the visitor to click through to another page?
Are the title and H1 accurate descriptions of the content rather than keyword variants of another page?
Would a customer still find the page useful if search traffic never arrived?

Google recommends people-first content with original information, substantial coverage, clear sourcing, and a satisfying answer. Adding 500 generic words does not prove any of those things. Improve the page only when you can add missing value, such as a tested process, real comparison, local constraint, original example, calculation, or evidence-backed decision framework.

Step 6: improve, merge, noindex, or remove

Improve the existing URL

Keep the URL when its intent is distinct and the page matters. Fix the specific technical problem, replace placeholder or duplicated sections, add the evidence the reader needs, strengthen relevant internal links, and update the title or heading only when the page's actual focus changed. Preserve the clean URL unless there is a compelling reason to move it.

Merge and permanently redirect

If two pages serve the same intent, move any genuinely useful material into the stronger page and use a server-side 301 or 308 redirect from the retired URL to the relevant destination. Do not redirect every removed page to the homepage. The target should be a sensible replacement for the visitor.

If indexing is only one part of a broader content cleanup, the old page decision framework adds search demand, business value, backlinks, and replacement intent to the choice.

Keep it for users but noindex it

Some pages are useful without belonging in search: internal search results, thank-you pages, account steps, filtered views, or short-lived campaign states. Use a robots meta tag or X-Robots-Tag with noindex, leave the URL crawlable so Google can see the rule, and remove it from the sitemap.

Remove it correctly

If the page is obsolete and has no replacement, return 404 or 410. A friendly not-found design can still help visitors, but the HTTP response must tell crawlers the resource is gone. Avoid an empty or error-like template that returns 200, which Google may classify as a soft 404.

Step 7: request indexing only after a meaningful change

After fixing an important individual URL, run the live test again. Confirm that the current response, rendered content, directives, and canonical declaration match the intended state. Then use Request indexing once. For many changed URLs, update the sitemap and let normal crawling work instead of submitting them one by one.

Google documents that crawling can take from a few days to a few weeks. It also states that a request does not guarantee immediate crawling or inclusion at all. There is no defensible fixed indexing SLA. Record the request date, the change made, and the next review date so you can distinguish waiting from repeated, evidence-free resubmission.

How to validate the result without chasing the report

Check	What it can tell you	What it cannot prove
URL Inspection indexed result	Google's stored index status, last crawl, and selected signals	That the live page is unchanged or currently ranking
Test live URL	Whether the current page can be fetched and appears technically indexable	Future indexing or canonical selection
Page indexing report	Patterns and counts across known URLs	A live verdict for every example URL
Search for the exact URL	Whether that URL currently appears for the test	Stable rankings, traffic, or impressions
Performance report	Impressions and clicks after Google begins serving the page	Guaranteed visibility for a newly indexed URL

Review the exact URL in URL Inspection and note the Page indexing report's own last-updated date. Do not keep changing a good page every few days because a grouped report has not moved. If the URL remains excluded after a fresh crawl, compare the rendered version and canonical signals again, then revisit whether the page is distinct enough to keep.

Practical questions

Is Crawled - currently not indexed a penalty?

The status itself is a page indexing classification, not a manual action notice. Check Search Console's separate Manual actions and Security issues reports if you suspect a site-level enforcement or security problem.

Will adding more words fix it?

Not by itself. Add information only when it makes the answer more original, complete, or useful. A longer duplicate remains a duplicate, and generic filler does not resolve a canonical, rendering, noindex, or soft 404 problem.

Should every URL in the report be indexed?

No. Redirects, obsolete URLs, feeds, filtered combinations, account steps, and intentionally excluded pages may be correct non-indexed outcomes. Prioritize URLs that are important to users and have a clear, unique search purpose.

Sources checked

Product behavior and documentation were verified against official Google sources on July 21, 2026.

<p class="cta

Update, Merge, Redirect, or Delete Old SEO Pages | FloxoLab

Mon, 05 Oct 2026 15:50:00 +0000

An old page can look weak in a traffic report and still be valuable. It may answer a seasonal question, support a customer after purchase, earn referral visits, convert a small number of high-value leads, or cover a narrow query that does not generate large impression counts. The opposite is also true: a page with impressions can be obsolete, misleading, or competing with a better page.

Treat content cleanup as a URL-by-URL business and search decision. Google recommends people-first content and warns against changing dates simply to make pages look fresh. There is no universal traffic threshold that tells you to delete a page, and content pruning is not an automatic ranking tactic.

Start with this decision table

What the evidence says	Best default action	What happens to the URL
The intent is still useful, and this is the right page to satisfy it	Update	Keep the same URL
Two pages satisfy essentially the same intent, and both contain useful material	Merge	Keep the stronger URL and permanently redirect the retired one
The content moved or has one clear, relevant replacement	Redirect	Return `301` or `308` to that replacement
Users still need the page, but it should not appear in search	Noindex	Keep a working `200` page with `noindex`
The page remains accurate, distinct, and useful despite low search traffic	Keep	Leave it available and monitor it
The page is obsolete, has no continuing value, and has no relevant replacement	Delete	Return `404` or `410`

Do not make the decision from clicks alone. Check the page's queries, impressions, seasonality, backlinks, referral traffic, conversions, internal role, accuracy, and closest replacement. A zero-click page may still deserve to stay, while a traffic-earning page may need an urgent accuracy update.

When an updated keeper becomes a genuinely useful resource, acquisition is a separate next job. Use the white-hat link-building guide to choose a citable asset, relevant publishers, and careful outreach. Do not treat a redirect or content cleanup as a link campaign by itself.

Step 1: collect evidence for the exact URL

Start with a long enough period to reveal seasonality. Search Console can show up to 16 months of performance data, so use the longest useful period when the business has it. Filter the Performance report by the exact page, then review clicks, impressions, and the queries that surfaced it. Google advises focusing on trends in impressions and clicks more than average position alone.

Export the page data and add business evidence that Search Console cannot provide. A compact audit sheet can include:

Current URL, title, status code, canonical, and indexability.
Clicks and impressions by month, plus the page's main queries.
Organic conversions, assisted conversions, and qualified enquiries.
External links, referral visits, and important bookmarks or campaigns.
Internal links and the page's role in a customer or support journey.
Accuracy, last meaningful update, and the cost of keeping it correct.
The closest competing or replacement URL and whether its intent matches.

Search Console assigns most performance data to Google's canonical URL. If the inspected URL is a duplicate, the clicks may appear under another page. Use URL Inspection to compare the user-declared and Google-selected canonicals before calling the page unused.

Step 2: decide whether the intent still deserves a page

Separate an old presentation from an obsolete purpose. A 2024 pricing comparison may still answer a live buying question, but its figures need replacement. A discontinued event registration page may have no ongoing purpose. An old annual report may remain a useful historical record and should not be rewritten as if it describes the present.

Ask four questions:

Is someone still likely to need this information? Consider customers and referral visitors, not only search volume.
Is the page's purpose distinct? A similar keyword does not always mean the same intent.
Can the information be made accurate? Some pages need a factual update; others describe a product or policy that no longer exists.
Is this the best URL to own the topic? If another page already does the job better, consolidation may be cleaner than maintaining both.

If two pages appear for the same query, first confirm that they truly compete. The Search Console cannibalization workflow shows how to compare URL intent instead of merging pages merely because they share words.

If the pages are still proposals rather than live URLs, use the small-site topic cluster collision test to define their jobs and reject unnecessary overlap before publication.

Choose update when the URL still owns the right intent

Update the existing page when its purpose remains valid and the URL is still the logical destination. Preserve accurate sections, replace obsolete facts, answer the current version of the question, fix broken references, and add missing evidence. A rewrite is not automatically better than a focused correction.

Keep the URL unless there is a real information architecture reason to move it. Changing a slug only to include a newer year or slightly different phrase creates redirect work and can break saved links. If the page is evergreen, remove unnecessary years from the title and body only when that makes the promise more accurate.

Update the visible date and structured data only after a meaningful content change. Google specifically asks whether a site changes page dates to make content seem fresh when the content has not substantially changed. The Article schema guide maps the visible publication and update dates to datePublished, dateModified, and the canonical article entity. Record what changed internally so the next reviewer can verify the date.

Choose merge when two pages should become one stronger answer

Merge when two pages serve the same search and user intent, neither needs to remain separate, and each has material worth preserving. Choose the keeper based on relevance and maintainability first, then consider links, conversions, historical performance, clean URL structure, and how well the URL matches the long-term topic.

Copy only useful, non-duplicative material from the retiring page.
Rewrite the keeper so it reads as one coherent answer, not two articles pasted together.
Update the title, headings, examples, sources, and visible modified date.
Publish and verify the keeper returns a direct 200 with a self-canonical.
Permanently redirect the retired URL directly to the keeper.
Update internal links, sitemap entries, structured data, hreflang where used, and campaign destinations.

Do not leave the old page live with a canonical to a substantially different article. Google recommends canonicalization for duplicate or very similar pages. A permanent redirect is clearer when an old page has actually been retired and replaced.

Choose a redirect only when the destination is relevant

Use a server-side 301 or 308 when content has permanently moved or a deleted page has a close replacement. Google treats permanent redirects as strong signals that the destination should be processed as the canonical. Point directly to the final URL and avoid chains.

Relevance is the control. An old service page can redirect to the current version of that service. An expired product can redirect to a true successor or a category that genuinely helps the same visitor. A deleted blog post about one narrow problem should not automatically redirect to the homepage or a generic blog index.

A redirect is not a disposal bin. Sending unrelated old URLs to one destination can confuse users and may be treated as a soft 404. If there is no useful replacement, a real not-found response is more honest.

Choose noindex when users need the page but search does not

Some pages have operational value without being useful search results: internal search screens, account steps, thin filter combinations, campaign confirmation pages, or private-facing instructions that are intentionally public. Keep the page working and add a robots noindex rule when it should remain accessible but not indexed.

If a template system keeps producing thin combinations, fix the generation rule before cleaning URLs one at a time. The programmatic SEO quality-gate guide defines dataset eligibility, duplicate boundaries, pilot review, and retirement states before those pages enter the index.

<meta name="robots" content="noindex">

Google must be able to crawl the page to see noindex. Do not block it in robots.txt and expect the meta rule to be read. Remove the URL from the XML sitemap because it is no longer an indexable destination. Noindex is not the right treatment for a page that has permanently moved, and it is not access control for confidential material.

Choose delete when nothing useful should replace the page

Delete a page when its purpose is gone, the information should not remain available, and no relevant destination satisfies the same need. Remove its internal links and sitemap entry, then return 404 Not Found or 410 Gone. Google's current crawling documentation says all 4xx responses except 429 are handled the same for this purpose: previously indexed URLs are removed over time.

A custom 404 page can help visitors find navigation or search, but the server must still return an actual 404 status. A friendly page that returns 200 can be classified as a soft 404. Do not use Search Console's Removals tool as routine cleanup. Google says the tool is temporary and is unnecessary for ordinary old URLs that return 404; crawlers will discover the change naturally.

Use keep when low traffic is the only problem

Keeping a page is a deliberate decision, not a failure to act. A page can remain as-is when it is accurate, useful, distinct, inexpensive to maintain, and connected to the site. Examples include compliance explanations, niche troubleshooting notes, seasonal services, historical case studies, and support content used by existing customers.

Low search volume means the ceiling may be low. It does not prove poor quality. Improve discovery if the page is orphaned, or clarify its title when impressions show the wrong expectation. If the page has no audience or role after that review, reconsider it during the next audit with better evidence.

Implementation checklist for every treatment

Action	Status and canonical	Links and sitemap	Validation
Update	Direct `200`, self-canonical	Keep preferred URL everywhere	Inspect rendered page and request indexing if important
Merge	Keeper `200`; retired URL `301`/`308`	Link and list only the keeper	Test content, redirect, canonical, and key links
Redirect	Direct permanent redirect to a relevant `200`	Replace old internal links and sitemap entry	Check first response and final destination
Noindex	`200` plus crawlable `noindex`	Remove from sitemap; retain user links as needed	Live-test the rendered robots rule
Keep	Direct `200`, self-canonical	Maintain meaningful internal links	Recheck accuracy on schedule
Delete	`404` or `410`	Remove internal links and sitemap entry	Confirm the server does not return a soft 404

If a cleanup creates redirected, non-canonical, or deleted sitemap entries, use the sitemap cleanup guide to repair the generator and validate the final inventory.

Measure the result without promising a deadline

Save a before snapshot with the decision date. After implementation, verify the live response, rendered canonical or robots rule, internal links, and sitemap first. Then use URL Inspection for critical URLs. Its indexed view reflects Google's stored copy, while the live test checks the current fetch and does not predict whether Google will index the page.

Compare Search Console periods only after enough time has passed to reduce daily noise. For an updated keeper, watch its queries, impressions, clicks, and conversions. For a merge, monitor the keeper and confirm internal crawls stop discovering the retired URL. For a deletion, expect the old URL to disappear over time rather than on a guaranteed schedule.

A decline is not automatically a failed cleanup. Demand, seasonality, rankings, titles, and reporting lag can all change the numbers. Compare like periods and check whether the remaining page now satisfies the intended query and business task.

Practical questions

Does deleting low-traffic content improve rankings?

Not automatically. Delete content because it is obsolete, misleading, duplicative without unique value, or unnecessary, not because it crossed an invented traffic threshold. Useful pages can have small audiences. Weak pages may be better candidates for an update or merge.

Is a 410 faster than a 404?

Do not choose between them as a ranking tactic. Google's current documentation groups 404 and 410 with the other ordinary 4xx responses for indexing. Use the status that accurately describes the server state and make sure the URL is removed from internal discovery and the sitemap.

How long should an old redirect remain?

Keep a useful permanent redirect while people, external links, bookmarks, or old materials may still request the URL. The current site should link directly to the final destination, but that does not make the redirect itself unnecessary.

Sources checked

Google's content, redirect, status-code, noindex, removal, canonical, and Search Console guidance was verified from official sources on July 22, 2026.

ArchiveMind

Mon, 05 Oct 2026 02:53:36 +0000

Inspiration
I built ArchiveMind because I had a drawer full of hard drives and could never find anything. I knew the files were there, but filenames and folder structures were often useless years later. I wanted a way to search my archive by what files actually contained instead of relying on remembering what I had named them.
What it does
ArchiveMind is a private, local-first desktop app that catalogs and searches large collections of files across folders, computers, and external hard drives.
Instead of forcing users to reorganize everything first, ArchiveMind indexes the files they already have and makes the archive searchable. The goal is simple: help people find files by what they contain, not just by filename.
ArchiveMind works locally, with no cloud storage required, no account, and no telemetry.
How I built it
ArchiveMind is built primarily in Python and uses SQLite with FTS5 for fast full-text search, along with LanceDB and local file extraction and indexing tools.
The desktop application uses pywebview to provide a native shell while keeping the search and cataloging system local to the user's computer.
I developed and tested ArchiveMind against my own real-world archive rather than a small demo collection.

SEO Automation with n8n: What to Automate Safely

Fri, 02 Oct 2026 15:50:00 +0000

SEO automation is safest when it collects evidence, applies repeatable rules, and asks a person to approve any change that could affect indexing, rankings, or published copy. n8n is useful for that middle layer. It can pull Search Console data, compare periods, filter noisy rows, log findings, and route a short review queue without being allowed to rewrite the site.

Partner disclosure. This guide includes a partner link to n8n Cloud. If you sign up through it, I may earn a commission at no extra cost to you.

That boundary matters. A workflow that says “these five pages lost impressions after a release” saves time. A workflow that changes five canonical tags because a metric moved can damage the site before anyone checks the reason.

Start with the native option

For an occasional check, use Search Console directly. Its Performance report already lets you filter by query, page, country, device, search appearance, and date. You can compare periods and export a table without building or maintaining a workflow.

n8n becomes useful when the work is recurring or needs more than one system:

run the same report every week;
compare a current window with a previous equivalent window;
ignore changes below a minimum impression threshold;
join SEO data with a release log or content inventory;
deduplicate alerts that have already been reviewed;
send different issues to different owners;
preserve an audit trail of what was detected and decided.

The automation should reduce repetitive preparation. It should not conceal how the decision was made.

Use a three-level safety model

Classify each SEO task before adding it to a workflow.

Level	Automation role	Examples	Default control
Observe	Read data and record facts	Search Console exports, sitemap checks, status monitoring	Can run unattended
Recommend	Apply rules and prepare a review queue	Flag falling pages, find sitemap mismatches, draft a title option	A person reviews the evidence
Change	Modify a public or indexable resource	Edit copy, redirects, canonicals, robots rules, internal links	Explicit approval plus rollback

Most small sites should keep their first SEO workflow in the first two levels. The potential gain from automatically changing a title is small compared with the cost of changing the wrong page or losing the original context.

What is generally safe to automate

Scheduled Search Console exports

Google provides a Search Analytics API for querying performance data. A request can group results by dimensions such as page, query, country, and device, and can apply filters before returning rows.

The API is not a complete event log. Google states that the service does not guarantee every row and returns top rows rather than all rows. Search Console also omits anonymized queries for privacy. Treat the export as strong first-party evidence with known limits, not an exhaustive ledger of every search.

Period comparisons with noise controls

A useful workflow can calculate:

click change = current clicks - previous clicks
impression change = current impressions - previous impressions
CTR change = current CTR - previous CTR

Do not alert on percentage change alone. A fall from two impressions to one is a 50 percent decline but is rarely a useful incident. Require a minimum volume and a meaningful absolute change.

review when:
current impressions >= 100
and absolute impression change >= 50
and percentage change <= -30%

Those values are starting rules, not universal SEO standards. Tune them to the size and volatility of the site.

Technical monitoring

n8n can schedule simple checks for:

important URLs returning a non-200 status;
sitemap URLs that redirect or fail;
canonical targets that no longer resolve;
a robots.txt or sitemap fetch that suddenly changes;
a critical page becoming unavailable;
a release list that does not match the expected public URLs.

Keep the monitor narrow: crawling every URL from a small n8n instance can overload the site, duplicate a proper crawler, or create false alarms from temporary rate limits.

Evidence packaging

The highest-value step is often the least dramatic one: build a review packet. Instead of sending “traffic down,” send:

affected URL;
metric and comparison windows;
absolute and percentage change;
minimum sample threshold;
recent release or content-change date;
current status code and canonical;
a link to Search Console for manual investigation;
the previous decision if the same issue was reviewed before.

That makes the alert actionable and keeps the workflow from pretending it knows the cause.

What should not run without review

Do not let a first SEO automation publish or change these items by itself:

titles, descriptions, headings, or body copy;
canonical tags;
redirects;
noindex, robots.txt, or crawl directives;
sitemap membership;
internal links at scale;
deletion or consolidation of pages;
repeated indexing requests;
AI-generated articles or local pages.

The same metric can have several causes. Falling clicks may reflect lower demand, a ranking change, a different result layout, a tracking issue, a migration, or a page that is intentionally targeting a narrower audience. A workflow can identify the symptom. It cannot infer the business decision from one number.

A safe weekly n8n workflow

The first version can use this sequence:

Schedule Trigger
  -> HTTP Request: Search Analytics API
  -> normalize rows
  -> compare with previous period
  -> apply volume and change thresholds
  -> check the alert ledger
  -> write a review record
  -> notify the owner

Step 1: choose equivalent periods

Compare like with like. A seven-day period can be compared with the previous seven days, but weekday patterns and holidays can still distort a small sample. For a low-volume site, 28-day windows are usually more stable. Record the exact dates because “last month” becomes ambiguous when somebody opens the alert later.

Step 2: query only the data you need

The Search Analytics API accepts a rowLimit from 1 to 25,000 and uses startRow for pagination. Google also warns that queries grouped or filtered by page and query can be more expensive against API load limits.

Start with the smallest useful query:

one search type;
one property;
only the required dimensions;
a bounded date range;
a row limit appropriate to the site.

Do not repeatedly query long historical ranges on every execution. Store completed period summaries and fetch only the window that needs updating.

Step 3: label preliminary data

Recent Search Console data can be incomplete. The API can return metadata showing that a result contains incomplete or still-processing data. A weekly report should either avoid the newest days or label them so a reviewer does not compare a final period with a preliminary one.

Step 4: normalize before comparing

Keep the comparison key explicit. If the workflow groups by page, normalize the public URL rules first but do not silently merge distinct pages. If it groups by query and page, remember that the available rows are still limited to the top data returned by Search Console.

Store raw input separately from calculated fields. That makes the result inspectable when a threshold behaves unexpectedly.

Step 5: prevent duplicate alerts

Create a stable key such as:

property + report_type + page + current_period_end

Before sending a notification, check whether that key is already in the alert ledger. Update an existing record when the evidence changes instead of creating a new task every time the workflow runs.

Step 6: notify, then wait for a decision

Send the review packet to email, Slack, Google Chat, Telegram, or the team’s normal task system. The notification should offer controlled outcomes such as investigate, accept as expected, create a content task, create a technical task, or snooze until more data exists.

For a workflow that must continue after a person responds, n8n can use a Wait step or an app operation that waits for approval. Record the reviewer, timestamp, and decision before any downstream action.

Example review logic

Finding	Workflow can do	Person must decide
Important URL returns 404	Capture response, timestamp, expected URL, and recent release	Restore, redirect, or intentionally retire
Sitemap URL redirects	List source and destination and check destination status	Update sitemap, redirect map, or page plan
Impressions fall 40 percent	Verify sample, compare periods, attach page and query rows	Whether demand, rankings, intent, or a site change caused it
Two pages appear for one query	Package page-level Search Console data	Whether intents differ or pages should be clarified or merged
CTR falls while impressions rise	Flag query and page combinations	Whether the snippet, ranking mix, or result layout explains it

When the finding concerns two competing URLs, use the full Search Console cannibalization diagnosis before changing either page. When a page is excluded, use the Crawled, currently not indexed decision guide rather than treating every exclusion as an error.

Add failure handling before trusting the report

The workflow itself needs monitoring. OAuth tokens expire, APIs return rate limits, schemas change, and a partial execution can send a misleading “all clear.”

Fail the report if the source request fails.
Record the number of source rows and filtered rows.
Distinguish “zero findings” from “no data received.”
Retry only temporary failures with a bounded policy.
Send exhausted failures to an Error Workflow.
Store the last successful run time.
Test with a known sample before scheduling production runs.

Use the failed n8n workflow debugging guide when a node fails, and add an n8n Error Workflow so a broken SEO report cannot fail silently.

Cloud or self-hosted n8n?

n8n Cloud is the simpler starting point for a small team because hosting, updates, and the workflow service are managed. Self-hosting can offer more infrastructure control, but it also makes backups, upgrades, security, uptime, and incident recovery your responsibility.

Choose based on operational responsibility, not on the SEO logic. The workflow should use least-privilege credentials either way. A read-only Search Console scope is preferable when the workflow only reads performance data. The n8n Cloud versus self-hosted cost guide compares the wider ownership trade-off.

A practical launch checklist

Begin with one property and one report.
Use read-only credentials.
Keep recent incomplete data out of final comparisons or label it.
Set minimum volume and absolute-change thresholds.
Store raw evidence and calculation inputs.
Deduplicate alerts.
Require a human decision for public site changes.
Add a rollback plan before automating any approved write.
Monitor the automation itself.
Review the rules after several real runs.

SEO automation is useful when it gives a person a shorter, better evidence queue. It becomes risky when the workflow converts an uncertain signal directly into a site change.

Sources checked

n8n partner link

Want managed n8n for the reporting workflow?

n8n Cloud is the simplest starting point if you want to build the reporting and approval logic without maintaining the workflow server. Affiliate disclosure: I may earn a commission if you sign up through this link, at no extra cost to you.

Try n8n Cloud

Need the SEO workflow mapped?

Send the property type, report frequency, decision threshold, and notification channel. I can map a read-only first version and define where human approval must remain.

Discuss the workflow

Originally published on FloxoLab.

Site Migration SEO Checklist: Redirect and Validate URLs

Thu, 01 Oct 2026 15:50:00 +0000

A safe site migration is an inventory and validation job, not just a redesign launch. Keep URLs when there is no good reason to change them. When a URL must move, send it through one direct permanent redirect to the closest useful replacement, update every internal signal, and verify the result at scale.

Google warns that ranking fluctuations can happen while it recrawls and reindexes changed URLs. Good preparation reduces avoidable losses, but it cannot promise a flat traffic line or a fixed recovery date.

Choose the checklist that matches the move

Migration	Main SEO risk	Required action
Redesign, same URLs	Content, links, headings, canonicals, or rendering change	Compare old and new pages; avoid unnecessary URL changes
CMS or URL structure change	Old URLs break or redirect incorrectly	Create a complete old-to-new map and test every route
Domain or subdomain move	Signals split across properties	Redirect, verify both properties, then use Change of Address where applicable
Hosting or CDN move, same URLs	DNS, capacity, firewall, or crawl access failure	Test infrastructure, preserve verification, and monitor server logs

Reduce simultaneous change. If possible, do not combine a new domain, new CMS, new URL structure, rewritten content, new analytics, and a new checkout in one untestable release.

Before launch: preserve a usable baseline

1. Crawl and export the old site

Save a crawl before development replaces the current version. At minimum, export each indexable URL, HTTP status, canonical, title, meta description, H1, robots directives, internal inlinks, depth, and structured-data status. Also retain:

XML sitemap URLs;
Search Console landing pages and queries;
analytics landing pages and conversions;
pages with external links;
images, PDFs, and other files that receive traffic or links;
robots.txt, redirects, and important response headers.

This baseline lets you distinguish a new launch defect from an old issue that already existed.

2. Decide which URLs actually need to change

A new CMS does not require new public URLs. Preserve a clean, useful URL when its page still solves the same task. Changing it creates redirect work, link updates, recrawling, and another failure point without creating value for the visitor.

Before adding a path to the migration map, apply the SEO-friendly URL design and change decision. It separates durable hierarchy and normalization fixes from cosmetic slug rewrites that should stay out of a risky launch.

If old content is being consolidated, use the update, merge, redirect, or delete framework before filling the map. Do not redirect every retired page to the homepage.

3. Build an old-to-new URL map

Use one row per old URL. A practical sheet includes:

old_url,new_url,decision,expected_status,owner,test_result,notes
https://example.com/old-chair,https://example.com/chairs/oak,redirect,301,developer,pending,closest replacement
https://example.com/expired-offer,,remove,410,developer,pending,no replacement

Every redirect destination should answer the same or a closely related need. A discontinued product may have a real successor. An unrelated article does not become relevant because both URLs are in the same spreadsheet.

4. Make the staging site testable but not indexable

Protect staging with authentication or another access control when possible. A temporary noindex rule can be useful on a public test host, but it must be removed from the production release. Do not block crawling with robots.txt and then assume a crawler has validated the pages behind the block.

Test pages, forms, images, downloads, navigation, mobile layouts, analytics, consent controls, and critical transactions. Confirm that the production host will have enough capacity. Google notes that crawl activity can increase after a move because both old and new URLs may be requested.

Use the mobile SEO checklist on representative templates before and after launch. It compares Googlebot Smartphone rendering, content and link parity, navigation, tap targets, and the real customer action instead of treating a responsive screenshot as proof.

5. Align the new site's signals

Each new indexable page should return 200, have a self-referencing canonical, remain crawlable and indexable, and appear in the new sitemap. Update internal links, hreflang annotations where used, structured data, Open Graph URLs, and asset paths to the new public URLs.

Use the Article schema guide for article-level entity and date checks. Use the sitemap cleanup workflow to keep redirect sources and noncanonical variants out of the final sitemap.

Launch: turn on direct permanent redirects

Use server-side 301 or 308 redirects for permanent moves when your platform supports them. Point each old URL directly to its final destination. Google can follow redirect chains, but chains add latency and create more places to fail.

old URL --301--> final new URL --200--> self-canonical

Avoid:
old URL --301--> interim URL --301--> another URL --200--> final page

Test the first response, the final status, the final URL, and the destination canonical. A browser reaching a page is not enough. It may have followed a chain, landed on an error template returning 200, or reached a page canonicalized elsewhere.

Use Change of Address only for the right move

Search Console's Change of Address tool is for a move from one domain or subdomain to another. Use it after redirects are working and both properties are verified. Do not use it for HTTP-to-HTTPS changes or for moving a few paths within the same site. Those moves rely on redirects and updated sitemaps.

For a domain move, verify all relevant variants and follow Google's property requirements. The tool supports the migration process, but it does not repair a broken redirect map.

Post-launch: run a crawl diff immediately

Crawl the public site and test the old URL list against production. Compare the results with the saved baseline.

Check	Pass condition	Failure response
Old URL routes	Direct 301/308 to the mapped destination	Fix missing, chained, looping, or irrelevant redirects
New indexable pages	200, indexable, self-canonical	Remove accidental noindex, blocks, or wrong canonicals
Internal links	Point directly to final new URLs	Update templates and content sources
Sitemap	Only live canonical new URLs	Repair the generator and resubmit
Assets and rendering	Critical CSS, JS, images, and files load	Fix paths, permissions, CDN, or firewall rules
Analytics and forms	Events and test submissions arrive once	Fix tags, consent, destinations, or duplicates

Monitor recovery without inventing an SLA

Track both old and new properties where relevant. Watch server logs, Page indexing, crawl errors, impressions, clicks, and key landing pages. Old URLs should lose activity as new URLs are crawled and shown. Investigate a persistent mismatch, such as old URLs still receiving internal links or new URLs returning unexpected statuses.

Google says a medium-sized site move can take a few weeks to be noticed, while larger sites can take longer. That is a general observation, not a deadline. Keep redirects for as long as possible, generally at least one year according to Google's current site-move guidance. For users and old external links, keeping useful redirects indefinitely is often sensible.

Compare equivalent weekly or monthly periods instead of reacting to one day. Separate migration effects from seasonality, campaigns, tracking changes, and wider search updates.

Common migration failures

Redirecting everything to the homepage

This removes the page-level relationship and can be treated as a soft 404. Redirect only to a useful replacement.

Launching production with staging noindex rules

Check the rendered HTML and HTTP headers, not only the CMS setting. Sample templates and crawl the full site.

Leaving old URLs in navigation and sitemaps

Redirects are a safety net for old requests. The new site should link directly to its final canonical URLs.

Judging success only by total sessions

Analytics can break during the same release. Validate tracking independently, then review Search Console and server evidence alongside business conversions.

Sources checked

Google's site-move, redirect, hosting, Search Console, and traffic-drop guidance was verified from official sources on July 26, 2026.

Need an independent migration check?

I can review the crawl baseline, URL map, redirect tests, canonical signals, sitemap, and post-launch diff before small defects become a sitewide traffic problem.

Request a technical SEO review

Originally published on FloxoLab.

How Long Does SEO Take? Measure Progress Before Traffic

Wed, 30 Sep 2026 15:50:00 +0000

There is no universal SEO waiting period. Google says a change may be reflected in a few hours, while other effects can take several months. It generally recommends waiting a few weeks before assessing whether work helped. That range covers very different events, from recrawling one title to reevaluating whether a site consistently provides useful content.

A responsible plan replaces “rank in 90 days” with a measurement chain: implementation, crawl access, indexation, impressions, relevant queries, clicks, and qualified leads. Each stage answers a different question and gives you a useful next action.

What should happen first?

Stage	Evidence	What it proves	What it does not prove
Implemented	Rendered page and release log	The intended change is live	Google has seen it
Crawlable	Live test, logs, status and robots checks	A crawler can access the page	The page will be indexed
Indexed	URL Inspection and Page indexing evidence	Google selected a version for its index	It will rank for a valuable query
Receiving impressions	Search Console Performance report	The page appeared in search results	The result attracted a click
Receiving relevant clicks	Page and query trends	Searchers reached the site	The visit created business value
Generating leads or sales	Analytics, CRM, calls, and form records	Organic visits contributed to an outcome	Every outcome was caused by one SEO task

Why one fixed SEO timeline is misleading

The same label covers work with different dependencies:

a title correction on a frequently crawled page;
a new page on a small site with few internal or external links;
a technical template fix across thousands of URLs;
a migration that changes every public URL;
a sitewide content improvement that must be evaluated over time;
a local service entering a crowded market with established competitors.

Google's own guidance separates fast reflection from slow evaluation. Its SEO Starter Guide says some changes can take a few hours and others several months. Its core-update guidance says sitewide helpfulness improvements may also take several months to be learned and confirmed. Neither page promises a positive effect.

A deadline is not evidence. An agency can control when it ships work and reports results. It cannot control when Google recrawls a URL, which canonical Google selects, how competitors change, or whether search demand grows.

If the business cannot wait for this organic evidence sequence, compare the timing and economics in the SEO versus Google Ads guide for Philippine small businesses instead of forcing SEO to behave like an on-demand traffic switch.

Start the clock after implementation, not after the invoice

If month one contains only meetings, research, and a slide deck, Google has no site change to process. Record the date each meaningful change goes live. Keep a simple implementation log with:

affected URLs or template;
problem and chosen change;
release date;
expected leading signal;
validation owner;
rollback or correction plan.

This is why a detailed SEO retainer scope matters. Activity such as “ongoing optimization” is hard to evaluate unless it names what changed and what evidence should move.

Checkpoint 1: confirm access and indexability

Before waiting for traffic, verify that the live URL returns the intended status, is not blocked by an accidental noindex rule, renders important content, uses the expected canonical, and receives crawlable internal links. URL Inspection can compare Google's indexed view with a live test, but a successful live test does not guarantee indexation.

If the page remains in Crawled - currently not indexed, use the evidence-based diagnosis workflow. Do not keep requesting indexing without improving the page or fixing the underlying signal.

Checkpoint 2: look for impressions and query fit

Once a page is indexed, Search Console impressions are the earliest useful visibility signal. Filter the Performance report to the page, then inspect its queries, countries, devices, and search appearance. Ask:

Are impressions increasing across comparable periods?
Do the queries match the page's intended task and geography?
Is visibility concentrated in one irrelevant query?
Are several pages competing for the same query?

An impression is not a visit, but it confirms that the page is entering real results. If two URLs keep appearing for one intent, use the Search Console cannibalization check before rewriting both pages around the same phrase.

Checkpoint 3: measure clicks and landing-page behavior

Clicks show that someone chose the result. Compare clicks with impressions and query relevance rather than reading CTR in isolation. A growing page can earn more impressions in lower positions and temporarily show a lower CTR. Search features, devices, branded queries, and result composition also change the comparison.

Use weekly or monthly granularity for longer trends. Search Console says these views smooth daily fluctuations such as weekends and holidays. Its newest data can be preliminary, so do not treat a dotted recent point as a final result.

The monthly SEO report guide explains how to connect pages and queries instead of accepting a screenshot of sitewide totals.

Checkpoint 4: connect organic visits to business outcomes

Rankings and clicks are intermediate signals. Define the useful outcome for the page:

a qualified form submission;
a booked consultation;
a phone call from the target service area;
an ecommerce order;
a repeat visit that later converts;
a download or signup that belongs in a real follow-up process.

Test forms and analytics before evaluating SEO. A missing event or broken thank-you page can make working acquisition look like zero results. Keep CRM source details where practical, and review lead quality rather than counting every spam submission equally.

Once you know the contribution profit of a closed customer, use the small-business SEO break-even model to convert qualified visits, lead rate, close rate, cost, and time into a decision. This keeps the timeline tied to business value instead of waiting for an arbitrary ranking date.

A practical review rhythm

This is an editorial measurement rhythm, not a promise of when rankings will improve:

When to review	Primary question	Action if the answer is no
Immediately after release	Is the correct change live and accessible?	Fix deployment, status, rendering, canonical, tracking, or links
After crawl evidence appears	Has Google fetched and processed the intended URL?	Check discovery, indexability, duplication, and server evidence
After enough comparable data exists	Are impressions and useful queries emerging?	Review intent, page value, internal links, and competition
Monthly or by campaign cycle	Are clicks and qualified outcomes trending in the right direction?	Separate technical, demand, snippet, conversion, and offer problems
Quarterly for broader strategy	Is the work creating a compounding set of useful pages and leads?	Change priorities, scope, or provider rather than repeating activity

Warning signs that waiting is not the answer

The work is still not live

Ask for release links and an implementation log. Research alone cannot change how the site is crawled or how a page answers a query.

Indexable pages return errors or conflicting signals

A 5xx response, accidental noindex, blocked resource, redirect loop, or canonical to another page is a defect to fix, not a maturation period.

Impressions grow only for irrelevant queries

The page may target the wrong task or be too vague. Recheck search intent and the business offer before adding more words.

Reports celebrate position while clicks and leads fall

Google recommends focusing more on trends in impressions and clicks than on absolute average position. Connect visibility to useful traffic and real outcomes.

Every quiet month produces another generic article

More URLs are not progress if they duplicate existing intent, remain unlinked, or never support a commercial path. The pre-engagement Search Console checklist helps establish whether the site needs technical fixes, content work, or no retainer at all.

Separate an SEO delay from a traffic drop

Search demand changes with seasons, news, competitors, and result layouts. Google recommends comparing equivalent periods and reviewing up to 16 months when diagnosing seasonality. If both impressions and clicks fall, inspect demand, indexing, site changes, and broad search updates. If impressions hold but clicks fall, review result presentation and competing results.

A recent site migration deserves its own crawl and redirect validation. Do not attribute a launch defect to “SEO taking time.”

Sources checked

Google's current timing, Search Console, performance-comparison, and traffic-drop guidance was verified from official sources on July 26, 2026.

Need a measurable SEO plan?

I can separate implementation from waiting, establish a Search Console baseline, and define checkpoints tied to crawl access, useful queries, qualified traffic, and leads.

Request an SEO review

Originally published on FloxoLab.

How to Get Cited in AI Search: Evidence, Structure, Limits

Mon, 28 Sep 2026 15:50:00 +0000

The practical goal is citation eligibility, not a guaranteed placement. A public page needs to be discoverable, understandable, specific enough to support a claim, and honest about where its evidence stops. Those same qualities improve the page for ordinary search and for the person reading it.

Google says its existing SEO fundamentals apply to AI Overviews and AI Mode, with no special markup or AI text file required. The llms.txt and AI crawler controls guide separates that optional context-file proposal from the robots, training, and infrastructure controls vendors actually document. OpenAI says allowing OAI-SearchBot is important for ChatGPT Search inclusion, but top placement cannot be guaranteed. Bing can report citations across supported Microsoft AI experiences, yet explicitly says citation counts are not rankings or authority scores.

What an AI citation proves

Evidence	Defensible statement	What it does not prove
Manual screenshot	This URL was cited for this prompt on this date	Stable visibility for the same prompt
Bing citation count	Bing reported this many citations in the selected period	Rank, authority, or placement in an answer
ChatGPT referral visit	A session arrived with a ChatGPT referral	Every citation or display of the page
Search Console Web traffic	Google Search traffic changed in this period	A separate count for AI Overviews or AI Mode

Record the observation, not the story you want it to tell. AI answers vary by prompt wording, location, time, retrieved sources, interface, and follow-up context.

Step 1: make the page eligible and accessible

For Google's AI features, a supporting page must be indexed and eligible to appear in Search with a snippet. Google lists no extra technical requirement beyond the normal Search rules.

Return a successful response for the canonical URL.
Allow Googlebot through robots.txt, the CDN, hosting firewall, and application layer.
Remove unintended noindex and restrictive snippet controls.
Keep important claims in rendered text, not only inside images.
Use crawlable internal links to the page.
Make structured data match the visible page.

For ChatGPT Search, confirm that OAI-SearchBot is not blocked and that the host or CDN permits OpenAI's published crawler IP ranges. OpenAI separates search discovery from potential training controls: OAI-SearchBot is used for search inclusion, while GPTBot is the control publishers can use for potential model training.

Do not paste a crawler rule into production without reading the existing robots policy. A misplaced wildcard can block more than one bot.

Step 2: answer one defined question

Open with a direct answer that states both the conclusion and its boundary. Then give each follow-up question a specific section.

Weak opening	Stronger opening
SEO retainers vary because every business is unique.	A small-business SEO retainer usually combines recurring technical checks, content improvement, internal linking, and performance review. The proposal should still name the monthly deliverables and who implements them.

The stronger version is concise but not absolute. It gives a system something useful to retrieve without hiding the condition that keeps the statement true.

Use headings that reflect real decisions, such as what is included, what is excluded, who owns implementation, and how results are measured. Do not create dozens of near-identical question headings simply to mimic possible prompts.

Step 3: keep evidence beside the claim

A concise passage is not automatically trustworthy. Scope makes it reusable. Put the unit, geography, time period, source, sample, exclusions, and verification date near any unstable number.

Observed result + scope + date + limitation

Monthly cost = platform fee + usage fees + maintenance time

Define every input to a formula and show a worked example. Label evidence as official documentation, first-party measurement, client result, estimate, or expert judgment. A planning estimate should expose its assumptions instead of borrowing the certainty of a measured result.

Link the primary source in the paragraph it supports. A long source list at the bottom is useful for review, but it should not force a reader to guess which source supports which number.

Step 4: publish differentiated utility

Rewriting the same consensus paragraph gives a small site little reason to be selected over another source. Add material the page actually owns:

a tested workflow and its failure path;
a before-and-after crawl;
a transparent cost calculation;
a reusable decision table;
an anonymized operational example with consent;
a reproducible method with explicit limitations.

Differentiated does not mean dramatic. A narrow observation with a method is more defensible than a broad claim that no reader can inspect.

Distribution does not make weak evidence citable. When a strong asset is ready for another audience, the digital PR versus guest posting comparison helps choose between uncertain journalist coverage and a narrower expert contribution without treating either channel as an AI-citation guarantee.

Recorded Copilot citation observations

On July 20, 2026, a manual Bing Copilot check for what does a typical SEO retainer include cited FloxoLab's SEO retainer guide beside a differentiated numerical claim.

The prompt, date, cited URL, surrounding answer, and screenshots were recorded. It was one observation, not proof of stable placement, sitewide authority, or a ranking. Copilot also widened the geographic context beyond the original statement. That scope drift is why qualifications should sit in the same sentence as the figure they constrain.

On July 27, 2026, a second manual check for typical SEO agency retainer inclusions extra costs cited the same guide in answer sections about common extra costs and proposal risks. The inline floxolab.com +1 labels show shared attribution, and the source card names the FloxoLab guide directly. These screenshots confirm another citation event. They do not prove that every bullet came from FloxoLab or that the page will appear for the query consistently.

Copilot included FloxoLab among the sources for a section about costs outside a base SEO retainer. Manual observation, July 27, 2026.

The same answer displayed the FloxoLab SEO retainer guide as a visible source card. One interface observation is evidence of citation, not a stable ranking.

Step 5: use structure without inventing AI schema

Helpful structure is ordinary editorial structure: one clear H1, a direct opening, descriptive H2 sections, short paragraphs, tables for repeated comparisons, and numbered steps for sequences. Keep important text visible and give the page an honest author and update date. The author authority guide explains how to connect that byline to relevant experience, inspectable work, and maintenance ownership.

Schema can describe a visible article, author, date, publisher, image, or breadcrumb when the vocabulary fits. It cannot turn an unsupported claim into evidence. Google says there is no special schema.org markup required for AI Overviews or AI Mode. The Article schema guide covers the supported implementation without creating an imaginary AI citation type.

Step 6: control duplicate and syndicated versions

If several URLs carry the same answer, a system may retrieve an old, parameterized, or syndicated copy. Keep one preferred canonical, link internally to it, list it in the sitemap, and redirect retired duplicates. Exact republications should use the original FloxoLab canonical and a visible source link.

Do not use rel="canonical" to settle two articles with genuinely different primary content. When first-party pages blur the same intent, use the Search Console cannibalization workflow to decide whether to clarify, merge, redirect, or reposition them.

Step 7: measure without inventing one visibility score

Google Search Console

Google includes AI feature activity within the normal Web search type. There is no separate filter in the Performance report, so an unexplained Web click should not be labeled as an AI Overview click.

Bing Webmaster Tools AI Performance

Bing's public-preview report includes total citations, average cited pages, grounding-query samples, page-level activity, and trends. Record the date range. Grounding queries are sampled, and citation counts do not show answer placement or page importance.

Analytics and manual observations

OpenAI says ChatGPT referral URLs include utm_source=chatgpt.com, which can help identify visits if the analytics setup preserves the parameter. A visit still does not reveal every citation. For manual tests, keep the prompt, interface, date, market, cited URL, attributed claim, and negative results.

Avoid these citation shortcuts

Machine-written volume: repeating existing summaries creates maintenance and overlap, not evidence.
Unsupported AI schema: Google explicitly says no special markup is needed.
llms.txt as a guarantee: do not let an experimental file replace crawlability, indexing, and page quality.
Cosmetic freshness: change authors and dates only when responsibility or useful content actually changes.
Information trapped in images: diagrams can support an explanation, but key claims must remain available as text.
Citation-only reporting: connect observations with traffic, engagement, leads, and the page's business role.

Citation-readiness checklist

The canonical page is public, crawlable, indexable, and snippet-eligible.
OAI-SearchBot is allowed if ChatGPT Search inclusion is desired.
A direct, bounded answer appears near the top.
Numbers have units, sources, dates, and assumptions.
First-party evidence includes a method and limitations.
Structured data matches the visible article.
Duplicate and syndicated copies point to the preferred URL.
Monitoring records prompts, dates, URLs, and negative observations.

The best preparation is not a trick for one interface. It is a page that a person can inspect, a crawler can access, and a system can quote without losing the conditions that make the answer true.

Sources checked

Platform behavior and measurement notes were verified from official Google, Microsoft, and OpenAI sources on July 27, 2026.

Need an evidence and technical review?

I can audit crawl access, canonical signals, claim boundaries, source quality, and measurement setup without promising placement in an AI answer.

Request an SEO audit

Originally published on FloxoLab.

Zero-Click Search: Measure Visibility Without the Click

Sun, 27 Sep 2026 15:50:00 +0000

Direct answer: do not measure zero-click search with a single percentage or replace clicks with an invented visibility score. Build a four-level scorecard: meaningful search impressions, actions completed on the search surface, website visits, and confirmed business outcomes. Report the levels separately because they use different counting rules and cannot be added into one conversion total.

This page handles the measurement problem. The AI search citation guide handles eligibility and content evidence, while the monthly SEO report guide explains the broader relationship between impressions, position, clicks, and qualified leads.

Zero-click is an outcome, not one report

A zero-click search is usually described as a search session that does not produce a visit to a third-party website. That label covers very different outcomes. A person may read enough to stop, refine the query, call a business from a profile, request directions, remember a brand for later, or receive an AI answer that cites a source without opening it.

These outcomes do not have the same value. A direction request for a clinic can be commercially useful. An informational impression with no later action may only show that the page was eligible to appear. A citation can prove that a system used the page as a source, but not that the citation created a lead.

The unobserved journey stays unobserved. If a person reads an answer, remembers the brand, and walks into a store two days later, no search report can reconstruct that exact path automatically. Use direct measurement where it exists, proxies where they are defensible, and label the gap instead of filling it with certainty.

Use a four-level measurement ladder

Level	What to record	What it proves	What it does not prove
1. Visibility	Relevant impressions, profile views, cited pages, citation counts	Your page or business appeared on a supported surface	Attention, preference, or revenue
2. Surface action	Calls, directions, bookings, messages, menu or product views	A measurable action occurred before a site visit	The action became a customer or came only from organic search
3. Website visit	Search clicks, landing-page visits, contact starts	The person reached the site	A sale or the full influence of earlier search exposure
4. Business outcome	Qualified lead, appointment, order, signed client, revenue	The business received an operational result	Exact search attribution unless the source was captured reliably

The ladder prevents two common reporting errors. First, it stops an impression from being presented as a conversion. Second, it stops a useful call or direction request from disappearing merely because the person did not load the website.

Match each surface to its own evidence

Surface	Best available evidence	Main limitation
Google web results	Search Console query and page metrics, plus the dedicated generative AI impression report when the property has access	The beta report is in limited rollout, records impressions rather than conversions, and remains included in the broader Web search type
Google Business Profile	Views, searches, calls, directions, website clicks, and applicable bookings	The performance report can include both organic and Google Ads activity
Microsoft AI surfaces	Bing Webmaster Tools AI Performance citations, cited pages, sampled grounding queries, and trends	Citations do not indicate placement, authority, or page importance
Other answer engines	Documented referral clicks plus a small repeatable prompt-and-citation sample	A manual prompt panel is a sample, not total audience measurement
Phone, reception, sales, or CRM	Lead source, first contact, qualification, appointment, and revenue status	Self-reported source data is incomplete and influenced by memory

Step 1: define the outcome before opening a dashboard

Choose the page or business area, the audience, and the action that matters. A service page may aim for calls or contact requests. An educational guide may aim for relevant visibility, later branded searches, and assisted leads. A local profile may aim for directions and bookings.

Write a short measurement contract:

Scope: dental implant service in Quezon City
Window: latest 28 complete days vs previous 28 complete days
Visibility: non-brand impressions for the service page and query family
Surface actions: Business Profile calls, directions, bookings
Website actions: search clicks and qualified contact starts
Business outcome: attended consultation and accepted treatment plan
Known gap: no exact link between a profile view and an untracked walk-in

This is more useful than starting with a sitewide zero-click percentage. It gives every number a reader, a purpose, and a business decision.

Step 2: use the dedicated Google AI report when available

Google documents Search Console impressions as appearances of links or content from your property, with counting rules that vary by result type. A click normally requires the person to leave Google for an external page. That difference makes impressions the closest first-party visibility signal when no site visit occurs.

Use complete and comparable date ranges. Avoid treating preliminary days as final.
Filter to the intended page or page group.
Inspect relevant query families rather than the sitewide total.
Separate branded and non-branded demand where the filter is available, or maintain a documented query pattern.
Compare impressions and clicks together, then inspect position and result context before explaining the change.

On June 3, 2026, Google announced dedicated generative AI performance reports for Search and Discover. The Search report separates impressions from AI Overviews and AI Mode and can group them by page, country, device, and date. It currently reports visibility through impressions, not a complete click-to-conversion journey. Google also says the same data remains included in the broader Web search type.

FloxoLab received access to the beta report by August 11, 2026. In the selected three-month view, Search Console recorded 174 generative AI impressions across 44 pages. The leading page was the automation services pillar with 81 impressions, followed by the n8n webhook troubleshooting guide with 19 and the homepage with 17. This is first-party evidence that FloxoLab URLs appeared in supported Google generative AI features. It is not a count of clicks, citations, rankings, leads, or unique people.

FloxoLab's Google Search Console Generative AI features report recorded 174 impressions in the selected three-month view. The beta report covers visibility in AI Overviews and AI Mode. Captured August 11, 2026.

The report attributed impressions to 44 FloxoLab pages. The visible top ten include service, troubleshooting, pricing, audit, and homepage URLs, so the total should be analysed page by page rather than treated as one sitewide conversion metric.

The report still carries a beta label and Google says it is rolling out to a subset of sites. Properties without access should continue using the ordinary Web report plus clearly labelled evidence from other platforms. Do not call a rise in Web impressions "AI Overview growth" when the property cannot isolate it.

Use the Search Console pre-audit for the initial query and page checks. If two URLs keep appearing for the same valuable query, move to the cannibalization diagnosis rather than assuming zero-click behavior caused the weak CTR.

Step 3: capture local actions outside the website

For a verified Google Business Profile, the Performance area can report views, searches, directions, calls, website clicks, and other interactions that apply to the business. A clinic may care more about calls, directions, and completed bookings than about whether the person visited the homepage first.

Read those metrics with their documented limits:

a call metric records clicks on the call button, not answered or qualified calls;
a direction request is an action, not proof that the person arrived;
a booking is only available when it is managed through a supported provider;
profile performance can include interactions from both organic results and Google Ads;
only metrics relevant to the profile appear, so different businesses may see different fields.

Connect the surface action to operations. Reception can tag whether a call was answered, whether the caller fit the service area, and whether an appointment was booked. That turns a button click into a business funnel without pretending Google supplied the entire chain.

Step 4: record AI citations as visibility, not conversions

Bing Webmaster Tools introduced an AI Performance report for supported Microsoft AI experiences. It can show total citations, cited pages, sampled grounding queries, and visibility trends. Microsoft explicitly says the figures do not indicate ranking, authority, placement, or the importance of a cited page.

FloxoLab's Bing Webmaster Tools AI Performance report showed 60 citations in the selected three-month window. The activity began from a small base and the visible grounding-query table was explicitly labelled as a sample. Captured August 2, 2026.

This is useful first-party evidence that FloxoLab pages are being cited across supported Microsoft AI experiences. It is not evidence of 60 visits, 60 leads, or a ranking position. The dashboard itself warns that the displayed activity is sampled and may be refined as more data is processed.

Use that report to answer narrow questions:

Which URLs are being referenced?
Which sampled grounding phrases are associated with them?
Did citation activity start, stop, or shift after a substantive update?
Does the cited page contain accurate and current evidence?

Do not assign a monetary value to every citation or combine citations with Search Console impressions. They come from different products and counting systems. For platforms without publisher-level totals, a fixed prompt panel can help with editorial QA, but it remains a sample. The citation guide explains how to improve eligibility without promising selection.

Step 5: connect search exposure to real business outcomes

The strongest measurement layer belongs to the business, not the search platform. Keep a small operational record of leads and customers with fields the team can actually maintain:

first contact date and channel;
service or product requested;
qualified or unqualified;
appointment, proposal, order, or closed status;
self-reported discovery source;
notes when the person mentions Google, Maps, an AI answer, or a specific article.

A simple "How did you find us?" field will not create perfect attribution. People forget, combine several touchpoints, or answer with the last thing they remember. It does provide useful directional evidence when the choices stay stable and staff do not guess on the customer's behalf.

Build one monthly scorecard, not one magic KPI

Metric	Current	Comparison	Interpretation	Next action
Relevant non-brand impressions	Record	Previous equal period	Visibility for the intended query family	Inspect page, query, and position changes
Business Profile calls and directions	Record separately	Same weekdays or year over year	Actions completed on the local surface	Check answer rate and appointment outcome
Cited pages and citation trend	Record where available	Same supported product and period	Source visibility in the measured AI surfaces	Verify factual accuracy and page fit
Search clicks	Record	Previous equal period	Visits sent from search	Review CTR only in page-query context
Qualified search-influenced leads	Record from operations	Monthly or quarterly	Commercial outcome with stated attribution quality	Improve source capture and follow-up

Add a confidence label beside every conclusion: direct, platform-reported, self-reported, inferred, or unknown. A smaller number with a clear origin is more useful than a larger blended score nobody can reproduce.

When no click is useful, neutral, or harmful

Pattern	Likely reading	Response
Relevant impressions rise, local calls and qualified appointments rise	Search visibility may be supporting real demand without requiring a site visit	Protect accuracy and improve operational source capture
Relevant impressions rise, citations appear, no commercial action is expected	The content may be serving an informational or authority job	Judge it by the page contract, not a service-page conversion target
Impressions rise on unrelated queries	Visibility expanded without useful audience fit	Correct the page focus or ignore the vanity total
Local views rise, calls and directions fall	The profile may be visible but unpersuasive, inaccurate, or seasonally mismatched	Check categories, hours, services, photos, reviews, and operational availability
Clicks fall after a search-layout change, business outcomes stay stable	More of the journey may be happening on the search surface	Keep monitoring before declaring an SEO loss
Clicks and qualified outcomes both fall	This is a real performance problem, not a zero-click success story	Diagnose query, page, position, indexing, local, and conversion changes

What not to do

Do not repeat a global zero-click percentage as your site result. The definition, market, device mix, and data source may not match your business.
Do not call every impression a brand exposure. Check that the query and page are relevant first.
Do not attribute all Web impressions to AI features. Use Google's dedicated generative AI report only when the property has access; otherwise the AI-feature data remains mixed into the broader Web search type.
Do not add ca

Do You Need llms.txt? AI Crawler Controls Explained

Fri, 25 Sep 2026 15:50:00 +0000

Direct answer: publish /llms.txt only if you maintain a documentation-heavy or structured knowledge site and can keep a curated machine-readable map accurate. For an ordinary service business, prioritize crawlable pages, internal links, a clean sitemap, correct structured data, and explicit crawler rules.

The distinction matters because llms.txt and robots.txt solve different problems. The llms.txt proposal describes a Markdown overview for use at inference time. Its own specification says it complements existing standards. It does not define access permission or an opt-out mechanism.

Use the control that matches the job

Control	Actual job	What it cannot promise
`robots.txt`	Tell compliant crawlers which paths they may request	Removal from search, privacy, or universal enforcement
`llms.txt`	Offer a curated Markdown description and links	Crawler access, training opt-out, ranking, or citation
`sitemap.xml`	List preferred indexable URLs for search discovery	Indexing or selection in an AI answer
`noindex` and snippet controls	Control indexing or how much Google may show from a page	A safe result when the crawler is blocked from reading the directive
CDN or WAF rules	Permit or deny requests at the infrastructure layer	Correct intent if rules rely only on a spoofable user-agent string

Do not treat a public text file as a privacy boundary. Never list private dashboards, customer portals, staging hosts, unpublished documents, or sensitive paths in llms.txt. Protect them with authentication and access controls.

What llms.txt is

The proposal places a Markdown file at /llms.txt. It starts with one required H1, may include a short summary and explanatory text, and can group useful links under H2 headings. The specification also proposes optional Markdown versions of detailed pages.

That can be useful for a software library, API, public knowledge base, or complex documentation set. A maintainer can point an agent toward a stable quick start, current reference, examples, and known limitations without asking it to infer the hierarchy from navigation and decorative HTML.

The proposal does not specify how an AI provider must discover, fetch, or use the file. It explicitly leaves processing decisions to each application. That is why publishing the file is an experiment, not an access-control project.

Why most small-business sites do not need it

A typical service site has a homepage, service pages, a few decision guides, contact information, and perhaps a local profile. Those pages should already explain the business clearly in rendered HTML. Adding another summary file creates a second place where services, locations, prices, policies, and URLs can become stale.

Google's official guidance is especially direct. Pages need normal Search eligibility for AI Overviews and AI Mode, and Google says no new machine-readable file, AI text file, or special markup is required. Googlebot access, indexability, internal discovery, visible text, page experience, and accurate structured data remain the foundation.

Site situation	Recommendation	Reason
Local or service business	Skip it for now	Improve the actual service pages and crawler access first
Small editorial site	Usually skip it	The sitemap, hubs, and contextual links already express the library
Large public documentation set	Consider a test	A curated route can reduce ambiguity for tools that choose to read it
API or developer product	Consider a generated file	Versioned references and examples may benefit from a concise machine-readable index
Site with weak crawlability	Fix access first	An optional file cannot repair blocked pages, bad status codes, or a hostile WAF

Separate search retrieval from model training

There is no single universal "AI bot" switch. Vendors document separate agents for different jobs, and a site owner may want search visibility without allowing potential training use.

Provider	Search or user retrieval	Separate control
Google	`Googlebot` controls Search, including AI Overviews and AI Mode	`Google-Extended` controls certain Gemini training and grounding uses outside Google Search
OpenAI	`OAI-SearchBot` supports ChatGPT search discovery	`GPTBot` is the published control for potential training
Anthropic	`Claude-SearchBot` and `Claude-User` support search and user-directed retrieval	`ClaudeBot` is used for content that could contribute to model training
Perplexity	`PerplexityBot` supports search results; `Perplexity-User` supports user-requested fetches	Perplexity says these two agents are not used to train foundation models

Google states that blocking Google-Extended does not affect inclusion or ranking in Google Search. OpenAI's publisher guidance similarly separates OAI-SearchBot from GPTBot. Anthropic documents three distinct agents so publishers can make separate choices.

Build the policy before editing robots.txt

Write the business decision first. Otherwise a copied rule can quietly block the exact search surface you intended to keep.

List the public content: decide which pages may be retrieved by search and user-directed agents.
Separate model development: decide whether to block training-specific agents where a vendor provides that control.
Protect private content properly: use authentication, authorization, network restrictions, or removal. Do not rely on crawler courtesy.
Inspect the whole delivery path: robots.txt, CDN, WAF, hosting firewall, rate limits, JavaScript challenges, and origin responses can disagree.
Record an owner and review date: crawler names, IP ranges, and product behavior change.

The AI search citation guide covers content eligibility and evidence after access is working. The technical SEO fixes guide covers infrastructure problems that ordinary content edits cannot solve.

A cautious robots.txt example

This example expresses one specific policy: allow documented search agents, block documented training controls, and leave normal search crawling open. It is not a universal recommendation. Read every vendor's current documentation and your existing robots file before adapting it.

User-agent: *
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: GPTBot
Disallow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: ClaudeBot
Disallow: /

User-agent: PerplexityBot
Allow: /

User-agent: Google-Extended
Disallow: /

Sitemap: https://example.com/sitemap.xml

This does not remove a page from search. A robots disallow can prevent a crawler from seeing a noindex directive on the blocked page. If removal is the goal, follow the search engine's documented removal or indexing controls instead of combining random directives.

It also does not create a hard security block. Robots rules are instructions for compliant agents. A scraper can ignore them, and a legitimate agent can still be stopped by an overly broad firewall rule.

Check the CDN and WAF separately

Allowing a crawler in robots.txt is only the first gate. OpenAI and Perplexity both tell publishers to check CDN, WAF, bot mitigation, response codes, and published IP ranges when access fails. Perplexity recommends combining the expected user agent with its current IP list rather than trusting the header alone.

A safe validation sequence is:

Request the live /robots.txt and confirm the deployed file matches the policy.
Request representative public URLs with the documented user-agent token.
Confirm a successful response, useful HTML, and no challenge page.
Inspect CDN and origin logs for 401, 403, 429, redirect loops, and unusually large responses.
Where the vendor publishes IP ranges, verify both the header and source range before creating an allow rule.
Recheck after deployment because caches and crawler processing can delay the observed change.

curl -I -A "OAI-SearchBot" https://example.com/important-page
curl -I -A "Claude-SearchBot" https://example.com/important-page
curl -I -A "PerplexityBot" https://example.com/important-page

A forged user-agent can pass this simple request test. Use it to find obvious blocks, not to authenticate crawler identity.

When an llms.txt test is worth maintaining

Consider a limited test when all of these conditions are true:

the public site contains a large, stable documentation or knowledge corpus;
the preferred entry points and current versions are difficult to infer from navigation alone;
the file can be generated from the same source of truth as the documentation;
every linked URL is public, canonical, useful, and maintained;
the team can test named tools or agents instead of treating the file as a universal standard;
removing the experiment would not damage ordinary crawling, indexing, or user navigation.

If you publish it, keep the file concise. Name the project, explain the scope, link only to preferred public resources, and record how it is generated. Do not paste your sitemap into Markdown or duplicate full pages into a second unmanaged content layer.

What not to do

Do not use llms.txt as an opt-out file. Use each provider's documented crawler token and access controls.
Do not block every AI-related token. A training control and a search bot may have different jobs.
Do not list sensitive paths. Public crawler files are not a substitute for authentication.
Do not create a stale second website map. Generate the file from maintained data or do not publish it.
Do not expect a citation lift. Access and context create eligibility, not selection.
Do not trust a user agent by itself. Use official IP data and logs when infrastructure policy depends on identity.
Do not let the experiment delay basic SEO. Fix status codes, internal links, canonicals, sitemaps, rendered text, and page quality first.

FloxoLab's current decision

FloxoLab does not need llms.txt to make its guides eligible for Google AI features or ChatGPT Search. The current priorities are a crawlable public library, one canonical URL per task, accurate metadata, responsive media, contextual links, and explicit crawler access.

A generated file may become worth testing after the SEO guide library expands and the filterable hub is stable. If that happens, the file should be derived from the content manifest, not maintained as another hand-written index. The topic-cluster guide explains why one source of truth matters when a library grows.

Decision checklist

The business goal is written before crawler rules are changed.
Search retrieval and potential training are treated as separate decisions.
Private content is protected with real access controls.
robots.txt, CDN, WAF, and origin behavior agree.
Official crawler documentation and IP sources were checked recently.
Important public pages return useful HTML to allowed agents.
An llms.txt experiment has a narrow purpose, owner, generator, and removal plan.
No ranking or citation outcome is promised.

For most small businesses, the right answer is simple: skip llms.txt for now, make the real pages easy to crawl and understand, and control each crawler according to the job it performs.

Sources checked

Behavior and crawler names were verified from primary or official documentation on August 2, 2026.

Need a crawler-access review?

I can review robots rules, CDN and WAF behavior, indexability, structured data, and AI-search access without selling an experimental file as a ranking shortcut.

Request an SEO audit

Originally published on FloxoLab.

AI Keyword Research: Cluster and Prioritize Ideas

Thu, 24 Sep 2026 15:50:00 +0000

Direct answer: use AI keyword research for expansion, normalization, classification, and cluster hypotheses. Do not use it as the source of search volume, ranking difficulty, current search intent, or business value. The reliable output is a short, evidence-backed queue of query families. It is not a list of hundreds of phrases ready to become pages.

This workflow stops at research prioritization. The topic cluster planning guide makes the later URL and internal-link decisions. If two live pages already appear for the same query family, use the Search Console cannibalization workflow instead of treating the problem as fresh keyword research.

What AI can and cannot do in keyword research

Job	Good use of AI	Evidence still required
Expand language	Suggest wording, modifiers, questions, and adjacent jobs from supplied seeds	Customer language, Search Console queries, sales notes, and support records
Clean a list	Normalize spelling, flag duplicates, and preserve a source reference	A human check that meaningful distinctions were not erased
Propose clusters	Group phrases by the reader's task and explain each proposed boundary	Current result-page review and a collision test before assigning URLs
Classify intent	Suggest informational, comparison, transactional, local, or navigational labels	Manual review because one phrase can support several situations
Estimate demand	Prepare candidates for tool checks	Search Console, Keyword Planner, Trends, and real customer frequency
Prioritize	Apply a scoring rule consistently to evidence you provide	Business fit, service capacity, proof, and the next useful action

Never ask the model to fill missing metrics. A plausible search-volume, CPC, trend, or difficulty number is still fabricated if it did not come from a named data source. Keep missing values blank and record what must be checked.

Step 1: begin with customer language, not an AI blank page

Collect the words people already use when a real problem is present. Useful sources include Search Console queries, sales-call summaries, contact forms, support tickets, internal site search, reviews, proposals, and objections recorded by staff. A small list of genuine questions is a stronger seed than a generic request for every keyword in an industry.

Remove names, email addresses, phone numbers, account details, confidential pricing, and customer-specific context before sending notes to an external AI service. Keep a neutral source label such as sales-call-07 or support-theme-refunds so every suggestion can be traced without exposing a person.

Start a research sheet with these fields:

Raw phrase: the wording as received, including awkward language.
Source: Search Console, customer call, ticket, review, or staff observation.
Offering and audience: the service or product and the person making the decision.
Problem stage: learning, comparing, buying, implementing, or troubleshooting.
Location or constraint: market, platform, budget, company size, or deadline when relevant.
Available proof: experience, screenshot, example, primary source, or measured result.

Step 2: expand candidates with a constrained prompt

Give the model the seed table and ask for controlled variations. Require a reason for every row and forbid invented metrics. The prompt below is deliberately narrower than “find keywords for my business.”

You are expanding a keyword research seed list.

Use only the business context and raw customer phrases below.
For each useful candidate, return:
- candidate_phrase
- source_seed
- reader_job
- likely_stage
- modifier_type
- ambiguity_or_missing_context
- evidence_needed

Rules:
1. Preserve meaningful customer wording.
2. Do not invent search volume, CPC, trend, competition, or rankings.
3. Do not turn simple synonyms or singular/plural variants into separate ideas.
4. Include a candidate only when it represents a real question, decision, or task.
5. Mark weak extrapolations as hypothesis.

Business context:
[paste a short factual description]

Sanitized seed rows:
[paste the seed table]

Review the result before continuing. Remove phrases that do not describe a useful reader job, promises the business cannot support, and variations created only by swapping adjectives. Keep the original source beside every surviving row.

Step 3: normalize and cluster by task

Clean obvious duplicates without destroying intent. Lowercase and trim whitespace for comparison, standardize spelling, and flag singular or plural variants. Preserve the original phrase in a separate column. Location, audience, platform, and problem-stage modifiers can change the job, so do not strip them automatically.

Then ask AI to propose clusters. A cluster is a shared reader task, not a bag of phrases containing the same noun.

Group these candidates by the reader's primary job.

For every proposed cluster, return:
- cluster_name
- one-sentence reader_job
- included candidate IDs
- phrases that look similar but must stay separate
- boundary_reason
- confidence: high, medium, or low

Do not merge candidates when they differ by:
- audience or decision maker
- problem stage
- local versus non-local need
- comparison versus implementation task
- troubleshooting versus general education

If the evidence is insufficient, place the candidate in "manual review".
Do not decide how many URLs to publish.

The final instruction matters. Query grouping happens before page architecture. One cluster may become a section, an existing-page update, a new guide, a service-page addition, or nothing at all.

Step 4: validate every cluster with named evidence

Source	Best question it answers	Limit to record
Customer and sales records	Do real prospects use this language or need this decision?	Small samples reflect the customers you already reach
Google Search Console	Which queries already produce impressions or clicks for this site and page?	Anonymous queries are omitted and the table exposes only top rows
Google Ads Keyword Planner	Is there approximate demand in a selected location and period?	Volumes are rounded, close variants are grouped, and advertiser competition is not SEO difficulty
Google Trends	Is relative interest rising, falling, seasonal, or regionally different?	Values are normalized from 0 to 100 and do not show absolute search volume
Current search results	What jobs and result types does the wording currently surface?	Results vary by location, time, language, and personalization context
Business evidence	Can this site give a useful, specific, supportable answer?	A keyword can have demand and still be a poor fit for the business

Search Console: first-party demand already touching your site

Start with the Performance report when the site already has data. Filter a relevant page, inspect its queries, and use a regular expression only when a well-defined phrase family needs grouping. Google omits anonymized queries for privacy and limits the table to top rows, so a visible query list is not the complete universe of searches. Bulk export provides the most complete query dataset when the property has enough data and the workflow justifies it.

Existing impressions are evidence of eligibility, not proof that a new URL is needed. Record the current page beside the query family. That single field helps prevent a research idea from competing with a page that already performs the job.

Keyword Planner: approximate market demand, not an organic forecast

Set the correct location, language, network, and date range. Google's average monthly searches include close variants and are rounded. Forecasts also depend on bid, budget, seasonality, and ad quality. Use the output as directional market evidence. Do not copy advertiser competition into a column called SEO difficulty, and do not present an ad forecast as expected organic traffic.

Google Trends: direction and seasonality, not volume

Compare candidates over the same geography and period. A Trends value of 100 marks the peak relative interest within that comparison, not one hundred searches. Low-volume phrases can display as zero. Compare a literal search term when wording matters and a topic when you need a broader concept across related terms or languages.

Manual result and evidence check

Open the live results for representative phrases and record what kind of task dominates: definition, step-by-step help, product category, comparison, local provider, tool, or troubleshooting. Do not imitate the top pages mechanically. The purpose is to test the cluster boundary and find what evidence a useful answer would need.

Step 5: score business fit before volume

Use a small scoring model that a second person can reproduce. The following ten-point model works well for a small content queue:

Business fit, 0 to 3: no meaningful connection, adjacent, relevant, or directly connected to a service and qualified next step.
Evidence, 0 to 3: unsupported, thin, adequate, or strong first-hand and primary-source support.
Task clarity, 0 to 2: ambiguous, partly defined, or one clear reader job distinct from existing pages.
Actionability, 0 to 2: passive information, a useful decision, or a practical next action the reader can complete.

Query family	Business fit	Evidence	Task clarity	Actionability	Total	Decision
AI keyword research for a small service business	3	3	2	2	10	Prioritize
Free keyword list generator	1	1	1	1	4	Hold or answer briefly
Best SEO tool	2	2	0	1	5	Narrow the task first
Guaranteed number-one ranking keywords	0	0	1	0	1	Reject the premise

Search demand can break a tie after the usefulness gates pass. It should not rescue a weak business fit, missing evidence, or a duplicate reader job. If a paid research platform would save time, the hands-on SE Ranking review shows what its keyword and competitor research can and cannot replace. A tool subscription does not remove the need for this evidence model.

Step 6: let AI apply the rule, not make the decision

Give the model only verified evidence and the scoring rubric. Require it to cite input fields and leave unsupported scores blank.

Score the validated query families using this rubric:
- business_fit: 0-3
- evidence_strength: 0-3
- task_clarity: 0-2
- actionability: 0-2

Use only the supplied evidence columns.
For each score, cite the exact input field that supports it.
If a field is missing, return "needs evidence" instead of guessing.
Flag any family already served by an existing URL.
Return a prioritized queue, a hold list, and a rejection list.
Do not recommend new URLs or page titles.

Review the ranking manually. A business constraint can override the total. For example, a high-scoring service topic should wait if the company cannot deliver that service, prove its claims, or handle the expected lead type.

The research handoff

The completed research sheet should contain one row per query family, not one row per wording variation:

representative query family and included variations;
reader job, audience, stage, and relevant location;
original source and sanitized customer language;
Search Console, Planner, Trends, and manual result evidence;
business fit, available proof, score, and uncertainty;
existing URL that may already serve the job;
status: prioritize, hold, reject, or investigate.

Stop here. The next step is the content map, where the prioritized families are tested against existing URLs and given distinct page jobs. This separation reduces cannibalization because research does not silently create one page per keyword. If one family reveals a repeatable set of real entities rather than ordinary editorial topics, use the programmatic SEO quality-gate workflow to test the dataset before generating pages.

Common failure modes

Starting from a generic AI prompt. The output reflects common web language, not evidence from your buyers.
Treating every variation as a separate opportunity. Singular, plural, and close wording often belong to one task.
Clustering by shared words. Similar vocabulary can hide different audiences, stages, and decisions.
Inventing metrics. AI cannot know your current Search Console data or live tool settings unless you provide them.
Sorting only by volume. A broad phrase can attract the wrong audience and consume evidence the business does not have.
Ignoring the existing URL column. A promising phrase may belong in an update, not a new article.
Uploading raw customer records. Sanitize notes and keep only the context needed for classification.
Publishing the whole queue. A prioritized hypothesis still needs a page contract, sources, and a collision check.

Decision checklist

Every candidate traces back to customer, search, market, or business evidence.
The model is forbidden from inventing volume, competition, trend, or rankings.
Clusters represent reader jobs, not repeated words.
Search Console query limits and anonymized data are acknowledged.
Keyword Planner settings and close-variant grouping are recorded.
Google Trends is used for relative interest, not absolute demand.
Business fit and available proof are scored before search volume.
Every family records an existing URL that might already serve it.
The output stops at prioritize, hold, reject, or investigate.
URL architecture and live cannibalization remain separate workflows.

Sources checked

Tool behavior and reporting limits were verified from official Google documentation on August 2, 2026.

Technical SEO Audit with Screaming Frog and Search Console

Wed, 23 Sep 2026 15:50:00 +0000

Direct answer: export or connect Search Console first, run a scoped Screaming Frog crawl, normalize both datasets to final canonical URLs, and compare the sets. Prioritize pages that already earn impressions or clicks, important pages Google knows but the crawl missed, and crawlable indexable pages with conflicting status, canonical, directive, or sitemap signals. Re-crawl after implementation, then use Search Console to confirm Google's stored view catches up.

The tools answer different questions. Screaming Frog reports what its configured crawler can reach and extract from the live site. Search Console reports Google's processed search and indexing evidence, with reporting limits and delays. Agreement raises confidence. A disagreement is a diagnosis lead, not an automatic error.

This guide starts after you have chosen the crawler and obtained safe viewing access. If you are comparing the free and paid versions, limitations, or whether the software suits you, read the separate Screaming Frog review. If someone else will access the property, define the minimum role using the SEO audit access guide.

Know what each dataset can prove

Evidence	Useful for	Does not prove
Screaming Frog crawl	Live response, internal discovery, directives, canonicals, links, metadata, and crawl depth under the chosen configuration	That Google discovered, rendered, selected, indexed, or ranked the same URL
Performance report	Pages and queries receiving reported Google Search impressions and clicks during the selected period	A complete URL inventory, current live status, or index status for every page
Page indexing report	Google-known URL totals, indexed and non-indexed groups, and representative examples by reason	That every non-indexed URL is an error or that every example can be exported
URL Inspection	Google's stored index view for one URL and a separate live fetch test	A guarantee that the page will appear or rank in search results

Google's Performance report documentation calls this canonical URL aggregation: most performance data is assigned to the page's canonical URL, not to a duplicate URL. That means a row may not use the exact URL variant that received the original request. Preserve the raw URL, but add a normalized join key rather than assuming a missing exact-string match means missing search evidence.

1. Define the scope and protect the baseline

Record the audit boundary before changing any crawler setting. Include the public host, allowed subdomains, staging exclusions, important folders, locale rules, parameter policy, expected canonical host, and the date range for Search Console. Save the raw exports and crawl file. You need the unchanged evidence when a filter or fix later changes the counts.

Property: https://example.com/
Audit date: 2026-08-04
Search Console period: last 90 days
Included hosts: example.com
Excluded areas: /account/, /checkout/, staging.example.com
Rendering: HTML / JavaScript
Canonical policy: HTTPS, non-www, no trailing slash
Expected indexable templates: service, category, product, guide

Do not aim an unrestricted crawl at infrastructure you do not own or have permission to test. Exclude private, transactional, faceted, calendar, and infinite URL spaces before starting. Use an appropriate crawl speed, especially on small or fragile hosting.

For a store-specific inventory that separates categories, products, variants, filters, pagination, stock states, and Product data, use the ecommerce SEO audit checklist after scoping the crawl.

2. Export the Google evidence before the crawl

In Search Console, choose the correct property and save these three views:

Performance, Pages. Use a meaningful comparison window, normally 90 days for a stable audit and longer when the business is seasonal. Export clicks, impressions, CTR, and position by page.
Page indexing. Record indexed and non-indexed totals, reasons, trend changes, and examples for the groups that affect intended pages.
Sitemaps. Record submitted files, last read state, and the relationship between submitted and discovered pages.

Search Console's ordinary report export is limited to the rows shown, and Google documents a maximum of 1,000 representative examples for several reports. Performance tables also omit some data for privacy and internal limits. Treat the export as valuable evidence, not a complete census. Larger properties may need the Search Console API or bulk export for fuller performance analysis.

Do not label every “Not indexed” group as a defect. Google explicitly notes that duplicates, alternates, redirects, blocked pages, and intentionally noindexed URLs can be legitimate. The audit question is whether the affected URL was intended to be a separate canonical search result.

3. Configure and run a reproducible crawl

Screaming Frog's default Spider mode is designed as a quick start, but the configuration still determines the evidence. Confirm these settings before pressing Start:

Start URL and host boundary. Use the preferred canonical origin and decide whether subdomains or external CDN hosts belong in scope.
Robots behavior. A normal crawl should respect the intended rules. If you test a second configuration that ignores them, label it clearly because it answers a different question.
Rendering. Start with HTML for a conventional server-rendered site. Use JavaScript rendering when important links, content, canonicals, or directives depend on client rendering.
Includes and excludes. Prevent session URLs, internal search, calendar loops, filter explosions, and private routes from consuming the crawl.
Sitemaps and external URL sources. Add the XML sitemap and Google-derived URLs when you need to find pages that are known elsewhere but not linked by the crawl.
Storage and speed. Choose settings the machine and server can sustain, then preserve them for the validation crawl.

After the crawl finishes, run Crawl Analysis so filters that depend on post-crawl calculations populate. Export the internal HTML inventory and the reports needed for redirect chains, canonicals, directives, response codes, crawl depth, inlinks, and sitemap membership. An issue count on the right side of the interface is not the deliverable. The affected URLs, source URLs, intended behavior, and fix owner are.

4. Connect Search Console or join the exports

The licensed integration can pull Search Analytics and optional URL Inspection data into the crawl. As verified on August 4, 2026, Screaming Frog documents the interface path as Configuration > API Access > Google Search Console. Focus URL Inspection on important templates because the API has a daily property quota and the crawler queries discovered URLs in crawl order unless you narrow the scope.

A manual join is equally valid for a small audit. Keep one row per observed URL, preserve each raw value, and create a consistent normalized key:

raw_url
normalized_url
crawl_status
indexability
declared_canonical
crawl_depth
internal_inlinks
in_sitemap
gsc_clicks
gsc_impressions
gsc_index_group
google_selected_canonical
decision
owner

Normalize only known presentation variants such as the canonical host, protocol, default port, and a documented trailing-slash rule. Do not strip meaningful parameters or merge paths because they look similar. Keep redirects and canonical targets in separate columns so the audit can reveal where variants converge.

5. Reconcile the URL sets

Observed state	Likely question	First check
Crawlable 200 + indexable + GSC performance	Is a valuable page technically stable?	Protect status, canonical, content, links, and search intent before changing it
GSC performance + missing from crawl	Is the page orphaned, redirected, blocked, outside scope, or represented by another variant?	Test the raw GSC URL, final response, inlinks, canonical, and crawl configuration
Crawlable indexable page + no performance row	Is it new, low demand, weakly linked, excluded from the export, or not selected for search?	Check launch date, Page indexing, intent, internal links, and a URL Inspection sample
Non-200 or non-indexable + GSC performance	Did a valuable URL change, or is historical/canonical data still being reported?	Inspect the date trend, redirect target, selected canonical, and replacement page
In sitemap + not internally discovered	Is the sitemap compensating for an orphan?	Find the intended hub, category, or contextual link path
Internally discovered + canonical points elsewhere	Are links promoting a duplicate?	Compare content, canonical intent, sitemap membership, and internal destinations

The most useful bucket is often “GSC evidence but missing from the crawl.” It can expose orphan pages, old URLs that still receive search activity, pages reachable only through a sitemap, or a crawler configuration that excluded an important section. The opposite bucket is not automatically bad. A live page with no Performance row may simply have no reported impressions during the selected period.

6. Prioritize impact before issue count

Do not sort the final backlog by the number of warnings. Score each finding across four dimensions:

Business and search value. Does the URL generate leads, sales, impressions, clicks, or support an important user journey?
Technical severity. Does the defect block fetching, indexing, canonical selection, navigation, or a final destination?
Pattern reach. Is this one stale page or a shared template, navigation component, routing rule, or sitemap generator?
Confidence. Do the crawl, Search Console, live page, and intended policy agree on the diagnosis?

Priority = value x severity x pattern reach x confidence

Critical: valuable URL unavailable, blocked, wrongly canonicalized, or removed without a valid replacement
High: repeatable template or navigation defect affecting intended pages
Investigate: evidence conflicts or the intended page job is unclear
Ignore: intentional state with no harmful discovery, index, or user impact

A missing meta description across 2,000 archive pages may be less urgent than one accidental noindex on the primary service page. A large redirect count may be expected history, while five redirecting links in the global navigation deserve a quick component fix.

Turn findings into fixable tickets

Each ticket should name the evidence, rule, shared source, sample URLs, owner, risk, rollback path, and validation method. “Fix 404s” is not enough. “Update the footer component so its four old routes link directly to final 200 destinations, then re-crawl every template using that footer” is testable.

Use the template-level technical SEO fixes when the diagnosis points to shared code. Use the on-page audit when one representative page needs content, heading, media, and internal-link review rather than a sitewide crawl fix.

What not to do

Do not export every issue and call it an audit. Filters report conditions. They do not know the page's job or business value.
Do not assume Screaming Frog is Google. A desktop crawl and Google's stored view differ in timing, discovery sources, rendering, and processing.
Do not treat missing Performance data as zero demand. The selected period, canonical aggregation, export limits, privacy filtering, and a new page can all affect the row set.
Do not force 100% index coverage. Legitimate duplicate, redirected, noindexed, and utility URLs should not all become canonical search results.
Do not change crawl settings between baseline and validation without recording it. Different scope can create a false improvement.
Do not request indexing before the fix is live. First verify the response, rendered output, directives, canonical, and internal links.

Validate the implementation in two stages

Stage one is immediate technical validation. Repeat the same scoped crawl, compare it with the saved baseline, and test representative affected URLs. Confirm the first response, final response, rendered directive, canonical, inlinks, sitemap membership, and template behavior. Make sure a falling issue count was caused by the fix rather than an exclusion or failed crawl.

Stage two is Google validation. Use URL Inspection on a small set of critical representatives. Compare Google's indexed view with the live test, then request indexing only when appropriate. Monitor the relevant Page indexing group and Performance pages over the following crawls. Search Console data can lag, so deployment success and Google processing are separate checkpoints.

Finding:
Affected pattern:
Baseline crawl file:
Search Console evidence:
Expected behavior:
Implementation owner:
Deployment date:
Same-config re-crawl result:
URL Inspection live result:
Google indexed-view follow-up:
Final decision: RESOLVED / MONITOR / REOPEN

Sources checked

Screaming Frog crawl configuration, Search Console integration, crawl analysis, and Google reporting and inspection behavior were verified against official documentation on August 4, 2026.

Need the crawl and Google evidence reconciled for you?

I can turn the URL sets into a prioritized implementation plan with affected patterns, owners, and validation checks, without handing over an unfiltered tool export.

<a href="https://floxolab

From a Test-Suite Trace to a Search Signal: the Bootstrap Pipeline Story

Tue, 22 Sep 2026 10:27:33 +0000

Where It Started

The problem to which everything traces back: RAG search across an unfamiliar codebase sees the code, but misses the intent. Embeddings find a chunk by keywords, PropertyGraph finds a symbol by name, but to the question "where is the real business logic here, and what can I safely throw away?" no model answers — because the answer simply doesn't exist in static code representation.

Hence the bootstrap pipeline was born for indexing a new project across 4 steps:

Entities — types and data-classes as the core domain backbone;
Entry points — decorators (@mcp_app.tool) as the outer system boundary;
Tests as ground truth — tests as the only deterministic way to say "this function is part of live execution logic";
Git → ADR — history of decisions extracted from commit logs.

Step 3 was the main battleground. The argument wasn't "are tests needed", but how to link a test to the exact function it actually executes. Steps 1 and 2 relied on clean static analysis, whereas step 3 lacked an obvious static answer.

First Clash: Static vs Dynamic (Exp 7)

Initial intuition: "A test has a name, a function has a name, let's link by name."
Measurement killed it instantly: 0 out of 109 tests in the evaluation sample named the function they actually executed. Import-only (file-level match) gave 77.9% — but file level is coarse noise (a single file contains dozens of functions).

We executed the entire suite (1,727 tests) using a custom sys.settrace plugin:

[dynamic_trace] total tests traced: 1727
[dynamic_trace] tests executing >=1 src function: 1551 (89.8%)
[dynamic_trace] unique src functions executed: 1212
[dynamic_trace] avg src functions per linked test: 10.1 (median 6, range 1-118)
tests with exact-name target hit in dynamic set: 47 (2.7%)
A/B same session: 174.8s vs 198.6s -> overhead +13.6%

Takeaway: Dynamic tracing is the only deterministic linker, at the cost of a +13.6% one-time execution overhead. And an uncomfortable truth surfaced immediately: a single test executes 10.1 functions on average. "1 test = 1 function" was a naive myth. Thus, edges required a ranker: which of the 10 is the primary target?

Ranking Failed (Exp 7b, Tarantula)

We tested the Tarantula heuristic ("a function called infrequently by many tests is the primary target").
Hypothesis: ≥60-70% of tests have an unambiguous candidate at rank≤3.
Reality:

rank≤3 applied to only 22.6% of tests (7.5% rank=1) — HYPOTHESIS REFUTED;
However, precision was high: manually inspected candidates at rank=1..3 were all accurate targets;
The main offender: shared utilities like safe_mkdir / get_data_root (autouse fixtures, 234 callers each) and project_hash (223 callers).

Verdict: Tarantula is unsuitable for selecting the main target, but works well as a confidence annotation for ~16% of tests. TESTS edges are thus built from the complete trace without truncation — they are correct by construction and do not require lossy ranking.

Driver Switch Failed (Exp 8, sysmon)

Could coverage run (Python 3.14, sys.monitoring) run faster than our custom sys.settrace plugin?
Hypothesis: Overhead <5%.
Measurement:

baseline: 184.88s | coverage: 221.78s -> overhead +19.96% (target <5% REFUTED)

coverage.py was ~1.5x slower than our lightweight plugin. sys.monitoring remains a validation oracle for spot-checks, while sys.settrace stays as the main execution driver.

Static Companion — Not a Replacement (Exp 9)

We evaluated a full static score (AST L1 calls / L2 name tokens / L3 imports) against dynamic trace as ground truth.

Signal	Hit	Recall	Precision	Mean Candidates
L1 (direct calls from test body)	88.4%	30.3%	68.0%	2.9
L2 (name tokens)	17.7%	3.8%	12.1%	—
L3 (file imports)	91.6%	72.0%	21.8%	41.4
Union (L1 + L2 + L3)	90.4%	70.0%	20.6%	—

The initial assumption (recall ≤ 30%) was wrong: union recall reached 70%. Static signals were stronger than anticipated, but as a precise anchor L1 is narrow (precision 68%, 2.9 candidates), and as a wide net L3 is noisy (41.4 candidates).

Verdict: Dynamic trace remains the edge driver; static analysis acts as a companion layer and candidate supplier for mock tests (which execute 0 real target functions dynamically).

Portability Across External Codebases (Exp 16)

Does this generalize beyond our own repo? We ran the tracer against external projects:

Project	Language	Tests	Linked %	Overhead
gemma_agent	Python	2882 (2874 pass)	97.3% (2805)	+17.4% (71.4s vs 60.8s)
commit-	Python	27	100%	N/A
codebase-memory-mcp	Go	27 test funcs	—	`go test`: 51.0% pkg / 22.2% per-test

Linked % on clean (non-mocked) third-party projects proved higher than on our own codebase (which relies heavily on mocks). The limitation is honest: dynamic execution is currently Python-only; Go and TS require per-test tooling (e.g., go test -coverprofile across N executions). PropertyGraph itself is polyglot, but the edge builder remains Python-first.

And Now: Edges Met the Consumer (E17)

Everything prior built test ──TESTS──> function edges inside PropertyGraph without leveraging them during search. E17 closed the loop:

Data: 1,727 tests → 16,172 TESTS edges, 1,595 Test nodes, 1,132 covered functions.
Implementation: SymbolIndexAdapter.get_tests_for_symbol() (incoming TESTS edges) + Searcher._append_tests_signal(): appends up to 3 tests per function (capped at min(len, 6) per query), graph_score = 0.4 vs 1.0 for definitions, sentinel chunk_index = -(20_000_000 + line) avoiding collisions with code chunks in RRF ranking.
Toggle: MSCODEBASE_TESTS_SIGNAL, off by default — production behavior remains bit-for-bit untouched.

A/B evaluation on a live PropertyGraph (7 target functions, true answers from trace):

hit@1: off=7/7, on=7/7 | hit@3: 7/7 | MRR(function): off=1.000, on=1.000
TESTS-signal: 6/7 queries received relevant covering tests in the response
graph_stage avg dt: off=3.43ms, on=3.27ms (within noise floor)
RETRACTION: 0 broken links (all files verified on disk)

The core invariant holds — function definitions are never displaced by test results (MRR = 1.0 in both arms): tests follow strictly as secondary context.

Wide Panel (35 queries, functions with most TESTS edges)

To validate beyond the narrow 7-query panel, we ran a wide panel of 35 identifier queries (functions with the most TESTS edges):

hit@1: off=33/35 (94.3%), on=33/35 (94.3%)
hit@3: off=34/35 (97.1%), on=34/35 (97.1%)
MRR(function): off=0.957, on=0.957
TESTS-signal: 34/35 queries received new covering tests (97.1%)
graph_stage avg dt: off=6.52ms, on=7.53ms (overhead +15.3%)

Critical finding: TESTS-signal does not improve hit@1 (off=on). It only adds context (tests) to already-found results: 97.1% of queries received new covering tests. This means TESTS-signal is context for LLM, not a search improvement. If LLM doesn't use tests, the signal is useless.

Language Coverage (Critical Limitation)

TESTS-signal works only for Python:

Python: 34.0% of functions covered by TESTS edges (1,108/3,256)
Other (Go, Rust, etc.): 0% (716 functions without TESTS edges)
TypeScript: 0% (11 functions without TESTS edges)

For non-Python projects, TESTS-signal does not work at all. Dynamic trace (pytest + sys.settrace) collects edges only for Python. For Go/TS, a separate connector is needed (go test -coverprofile, Jest coverage), but this is not done.

Red Team: 5/5 Attacks Repelled

We tested TESTS-signal against 5 attack vectors:

✅ Concurrency: 10 threads × 100 calls = 1,000 calls in 17.2s, 0 errors
✅ Boundaries: function with 234 tests = 16.11ms (acceptable)
✅ Abuse: query for nonexistent function = 0 results (graceful degradation)
✅ TOCTOU: graph closed between calls = graceful degradation
✅ Dependency failure: PropertyGraph with nonexistent path = 0 results (graceful degradation)

Conclusion: TESTS-signal is resilient to concurrency, boundaries, abuse, TOCTOU, and dependency failures.

What Could Go Wrong

A transparent list of risks and open validation items. (Full numbers for the A/B and red-team results are in the E17 section above — this list stays to the takeaways and the fixes.)

Evaluation scope. While expanded to a 35-query panel, evaluation is still performed on a single primary codebase without deep reranker interaction.
A/B did not improve hit@1. See "Wide Panel" above — TESTS-signal does not help find the function. It only adds context to already-found results.
→ Conclusion: TESTS-signal is context for LLM, not a search improvement.
→ Risk: if LLM doesn't use tests, the signal is useless.
→ Fix: verify on real LLM pipeline (not in this experiment).
Overhead +15.3% for wide panel (6.52ms → 7.53ms avg graph_stage time). For bootstrap (one-time run) this is acceptable. For prod search — may be critical with many queries.
→ Risk: at 1000 queries/sec, overhead may be noticeable.
→ Fix: cache TESTS-signal (not done).
Language limitation. Dynamic trace is currently Python-only (~34% function coverage in Python, 0% in JS/TS/Go).
graph_score = 0.4 is an empirical constant. Chosen to stay strictly below function definitions, but unverified against BM25/reranker weight interactions.
→ Verify on full pipeline; constant may become a parameter.
Pointer :0. Test nodes from dynamic trace lack line numbers (line=0). Indexers must resolve test decorator line positions before enabling in prod.
Hub-function noise. safe_mkdir linked to 234 tests yields low-signal noise. The cap of 3 tests prevents payload flooding but doesn't solve irrelevance.
Dependence on a green test suite. On broken test suites, trace degrades (failing tests = missing edges). Bootstrap applies to stable branches only.
Mock tests are blind. 10.2% of tests execute 0 src functions; static companions cover 88 of 176, but not all.
Graph reindex drift. Rebuilding the PropertyGraph may alter node ordering slightly.
CI scale limit. Running trace on 100k+ test suites may breach CI execution windows.
Clean-state status. Verification was executed locally; clean CI state verification requires a PR merge.

Acknowledgments

A huge thank you to everyone who engages with these posts in the comments. Your feedback, real-world observations, counter-examples, and benchmark numbers directly shape these experiments. This kind of open technical critique is what keeps engineering honest.

A note on how this was written

Every experiment, bug, failure, and idea here is mine — I earned them the hard way, in production, in public. AI worked as my editor: it helped me structure thoughts and polish my English. It did not invent the facts, because it has none of its own.

No AI detectors were consulted in the making of this disclosure. They have enough trouble agreeing on what I am.

Disclaimer & Status: draft (source-material for the article). This is not a "feature advertisement", but an honest engineering story: figures are reproducible, weak points are named, and unaddressed risks are listed in the "What Could Go Wrong" section.

On-Page SEO Audit Checklist: Fix What Actually Matters

Mon, 21 Sep 2026 15:50:00 +0000

Direct answer: audit one page in this order: confirm the intended query and page job, verify that the canonical URL is indexable, compare the search result promise with the visible page, inspect the title and main heading, evaluate the main content, check internal links and media, validate applicable structured data, then measure the released change. A tool score is supporting evidence, not the audit result.

This sequence prevents a common waste: polishing keywords, headings, and descriptions on a page that targets the wrong task, is not the selected canonical, or has no useful path into the rest of the site.

This is a page-level workflow. Use it on one important service, product, category, location, or article URL at a time. A whole-site SEO audit has a different job: it crawls the full inventory, finds repeated template and indexation problems, and prioritizes them across the site.

Start with one page, one query family, and one outcome

Choose a page that matters to the business or already has search evidence. Good candidates include a commercial page with impressions but few clicks, a page close to the first results page, a page whose traffic declined, or a representative URL from a reusable template.

Record the audit boundary before opening an SEO tool:

Page: https://example.com/service
Primary task: compare and request this service
Query family: [main query and close variants]
Audience and market: [who and where]
Desired action: [contact, purchase, booking, next page]
Current evidence: [impressions, clicks, CTR, position, conversions]
Audit decision: pass / fix / investigate

Search Console can show the queries for which a URL already appears. Filter the Performance report to the exact page, then inspect its queries, countries, devices, impressions, clicks, and CTR. If the page has no data yet, define the task from real customer language and compare the live results manually. Do not invent precision from a third-party volume estimate.

The ordered on-page audit

Order	Decision	Evidence	Typical action
1	Can this URL appear?	Status, robots state, canonical, rendered HTML	Fix eligibility or choose the intended canonical before editing copy
2	Does it own the right task?	Queries, search results, page purpose, competing site URLs	Keep, refocus, consolidate, or choose a different page
3	Does the search preview set the right expectation?	Title link, snippet, visible promise	Rewrite the title or description without promising content the page lacks
4	Does the page complete the task?	H1, opening answer, evidence, details, next action	Add missing decision information, remove repetition, clarify ownership
5	Is the page connected and usable?	Internal links, anchors, images, layout, mobile view	Repair discovery, context, accessibility, and delivery
6	Did the release work?	Live render, validation, annotations, later search trends	Confirm the output, then observe instead of repeatedly rewriting

Use pass when the evidence supports the intended job, fix when the correction is clear, and investigate when the symptom may come from another page, a template, or a sitewide system. An arbitrary 73/100 score hides those distinctions.

1. Confirm index eligibility and the intended canonical

Inspect the exact clean URL in Search Console. Check the indexed status, last crawl, declared canonical, Google-selected canonical, and any indexing blocker. Run the live test after a change and inspect the rendered screenshot and HTML when the page depends on client-side rendering.

Before changing the page, confirm these five conditions:

The URL returns the intended page with a successful response.
It is not blocked by a noindex rule, robots restriction, login, or accidental header.
The canonical points to the URL that should collect signals.
The rendered HTML contains the important title, main content, links, and media.
The page is linked from a useful parent or related page, not only listed in a sitemap.

A live-test pass means the page appears eligible, not that it is indexed or will rank. If Google selects another canonical, diagnose why before rewriting the page. Duplicate jobs, inconsistent internal links, redirects, and template rules often need a broader implementation fix.

2. Check whether the page owns the right search task

Read the current search results for the main query and close variants. Classify the job they satisfy: learn, compare, buy, visit, troubleshoot, calculate, or complete a specific task. Then ask whether your page belongs in that set and whether another page on your own site is a closer match.

Search intent is not a fixed label from a keyword tool. It is an evidence-based description of what the current result set helps users do. Mixed results can indicate several valid tasks, not one mandatory page format.

Compare the page with the result set on useful dimensions: audience, geography, product or service type, decision stage, expected evidence, freshness, and next action. Do not copy the competitors' section order. Identify what a qualified visitor still needs to decide or complete.

If two of your pages answer the same task, changing both titles to slightly different keyword variants does not create a meaningful boundary. Choose one owner, then update, merge, redirect, or reposition the other page. The keyword cannibalization guide covers that site-level decision.

3. Audit the title link, H1, and search snippet together

The HTML <title> should be unique, descriptive, concise, and accurate. The visible H1 can be more explanatory, but it should describe the same page. Google can form title links from the title element, visible headings, prominent text, and links that point to the page. It primarily builds snippets from page content and may use the meta description. Treat the title, H1, opening, and description as one promise, not four independent keyword fields.

Check four things:

Identity: the title and H1 name the page's actual task or offering.
Specificity: location, audience, format, or constraint appears only when it changes the decision.
Consistency: the title, H1, opening paragraph, and internal anchors do not describe different pages.
Restraint: no repeated keyword list, unsupported superlative, fake freshness, or truncated boilerplate.

Write a page-specific meta description that states the useful outcome and a meaningful boundary. The visible opening should make the same promise if it becomes the snippet.

4. Audit the main content as a decision path

Read the page without its navigation, design, or keyword highlights. Can a qualified visitor understand the answer, verify it, deal with exceptions, and take the next useful action?

Layer	Pass condition	Common failure
Opening	Answers the primary question or states the decision boundary early	Long setup that withholds the answer
Coverage	Handles the necessary choices, steps, constraints, and failure path	More words without resolving the next question
Evidence	Important claims have a source, method, example, screenshot, calculation, or firsthand observation	Generic claims that any competing page could make
Scope	Geography, date, units, audience, and exclusions stay beside qualified claims	A narrow fact is written as a universal rule
Ownership	A visible author and verification date make responsibility clear where readers expect them	Anonymous copy with no maintenance owner
Action	The next step follows from the page's task	A sales CTA interrupts before the page earns it

Google's people-first self-assessment asks whether content provides original information or analysis, adds substantial value beyond its sources, uses a descriptive title, and leaves the reader able to achieve the goal. Those are better audit questions than keyword density or a preferred word count. Google explicitly says it has no preferred word count.

Remove passages that repeat the same answer in the introduction, table, body, Q&A, and conclusion. Add material only when it answers a distinct follow-up question or supplies evidence the page currently lacks.

5. Check internal links in both directions

An important page needs contextual links from pages a user would naturally visit before it. It also needs useful routes onward. Inspect the links in the rendered HTML, not only the CMS editor.

At least one relevant page links to this URL with a normal crawlable <a href>.
Anchor text describes the destination without forcing an exact keyword phrase.
Links point directly to the final clean URL instead of an internal redirect.
The page links to evidence, prerequisite tasks, deeper implementation, and the next decision where useful.
Broken, obsolete, and unrelated links are removed or replaced.

Read only the anchor texts on the page. If they are mostly “click here,” “learn more,” or repeated commercial phrases, the link layer is not doing enough explanatory work. Google's link guidance says descriptive, concise anchors help both people and Google understand the destination.

6. Audit media for meaning, accessibility, and delivery

Keep an image when it explains, proves, or helps choose something. Decorative images can remain visually useful, but they should not carry essential information that is missing from the text.

Use normal <img> markup with a real src fallback, even when picture or srcset provides responsive formats.
Write contextual alt text for informative images. Use empty alt text for purely decorative images.
Place the image beside the text it supports and use a caption when the reader needs source or interpretation context.
Declare width and height so the layout reserves space.
Serve an appropriately sized compressed file instead of making every phone download the desktop source.
Do not present a generated vendor interface as a real product screenshot.

If loading or layout instability is the problem, follow the separate Core Web Vitals diagnosis. A page audit should note the symptom and evidence, not replace a full performance investigation with a compressed-image checkbox.

7. Validate only the structured data the page can support

Structured data should describe the visible page and use a type Google supports for the actual content. Run the Rich Results Test, check required properties, and compare every material field with what a person can see.

Valid syntax does not guarantee a rich result or better rankings. Do not add irrelevant types, hidden claims, invented ratings, or deprecated FAQ markup to make a validator look busier. For article pages, the Article schema guide covers authorship, dates, images, and breadcrumb relationships in detail.

8. Release one coherent change set and verify it

Record what changed and why. Check the public URL after deployment, not only the preview:

the final response, canonical, robots state, title, description, H1, and important links are correct;
the mobile layout preserves the content and next action;
the live URL Inspection render contains the expected HTML and media;
the Rich Results Test reports only the intended entities and warnings are understood;
the sitemap and internal links use the final canonical URL;
the release date and hypothesis are annotated for later comparison.

Then allow enough time for recrawling and search data. Filter Search Console to the page and compare a suitable period with the preceding one. Watch the intended queries, impressions, clicks, CTR, and qualified actions. A title change can affect CTR before position; a content or internal-link change may take longer. Google notes that external events and competitor changes can also move the numbers, so timing is evidence, not proof of causation.

What not to do

Do not optimize toward a plugin score. The score cannot decide whether the page owns the right task or offers useful evidence.
Do not force an exact keyword into every element. Repetition can make titles, headings, anchors, alt text, and copy less useful.
Do not add words to hit a target. Add a missing answer, proof, choice, failure path, or next step.
Do not change the URL for style. A readable existing URL can stay; a change creates redirect, linking, sitemap, and measurement work.
Do not treat a rewritten snippet as a bug by itself. Google can select a different title link or snippet from the page for a specific query.
Do not fix a repeated template problem on one page. Escalate duplicated titles, canonicals, navigation, or schema to the system that generates them.
Do not publish several speculative rewrites at once. A coherent hypothesis is easier to verify and reverse.

Final page-audit record

Finish with decisions, not a screenshot of warnings:

Page job: PASS / FIX / INVESTIGATE
Index eligibility: PASS / FIX / INVESTIGATE
Title and snippet: PASS / FIX / INVESTIGATE
Main content and evidence: PASS / FIX / INVESTIGATE
Internal links: PASS / FIX / INVESTIGATE
Media and mobile delivery: PASS / FIX / INVESTIGATE
Structured data: PASS / NOT APPLICABLE / FIX

Highest-impact change:
Evidence for the change:
Owner and release date:
Validation method:
Next review date:

If the highest-impact issue is specific to this page, fix and verify it. If it repeats across a template or many URLs, move into the template-level technical SEO workflow. That boundary keeps a one-page checklist from turning into a disguised sitewide audit.

Sources checked

On-page, rendering, linking, image, structured-data, and Search Console guidance was verified from official Google documentation on August 4, 2026.

Brand SERP Audit: Control What Customers Find First

Wed, 16 Sep 2026 15:50:00 +0000

Direct answer: search the exact brand name and its important variations, record the first page as a customer sees it, and classify every result as owned, managed, influenceable, reportable, or monitor-only. Fix contradictory facts and weak owned pages first. Then claim eligible profiles, respond to genuine reviews through an operational process, and use removal or reporting tools only when the content meets their rules. You can improve the evidence around a brand. You cannot reserve or fully control a search results page.

A brand SERP audit is narrower than a general SEO audit. It asks what appears when someone already knows the name and wants to verify the business, find the official site, read reviews, contact the right location, or investigate a concern. It does not audit every non-branded keyword, local ranking factor, or backlink.

1. Build a repeatable query set

Write the queries before searching so the next audit uses the same scope. Include only variations that represent a real customer task. A practical set for a small business is:

[exact brand name]
[brand name] + [city or country]
[brand name] reviews
[brand name] contact
[brand name] pricing
[brand name] login
[brand name] + [founder name, if customers use it]
[common misspelling]
[domain without https or www]

Business type	Useful query modifiers
SaaS	`login`, `status`, `pricing`, `security`, `integrations`
Local service	`[city]`, `reviews`, `hours`, `directions`, `phone`
Ecommerce	`shipping`, `returns`, `customer service`, `order tracking`
Personal brand	`[company]`, `speaking`, `publications`, `contact`

Use these as prompts, not a mandatory checklist. Keep only modifiers that represent real customer tasks for the business.

Do not assume one search is universal. Results can vary by country, language, device, time, and search context. Google itself suggests private browsing when checking how others view a Business Profile, but a private window is still not a neutral global rank tracker. Record the environment and treat each capture as a sample.

captured_at
query
country_and_city
language
device
signed_in: yes / no
result_position_or_feature
result_url_or_profile
result_title
owner
classification
issue
evidence
next_action

Capture the full first page and the visible profile or panel. Save the search date and take a screenshot for the audit record. Do not automate high-volume scraping against a search interface. A small, intentional sample is enough to prioritize a brand audit.

2. Classify every result by the action you can actually take

Class	Examples	Available action
Owned	Official website, support page, location page, newsroom, author page	Edit, redirect, noindex, secure, or improve internal discovery
Managed	Google Business Profile, verified social profile, marketplace account	Claim access and update within platform rules
Influenceable	Independent directory, press article, customer forum, review platform	Ask the publisher to correct facts, respond, or provide better public evidence
Reportable	Impersonation, phishing, exposed personal data, prohibited review, illegal content	Use the specific platform, security, privacy, or legal route with evidence
Monitor-only	Accurate criticism, lawful news, ordinary third-party commentary	Address the underlying issue and publish useful evidence, not a removal threat

The classification prevents wasted effort. A poor title on an owned page is a direct fix. A wrong phone number in a managed profile needs a profile update. A factual error in a third-party directory needs a correction request. A genuine negative article is not removed just because the business dislikes it.

Do not sell or buy "full control" of page one. Search results are generated from many sources and change over time. The realistic job is to make official evidence clear, consistent, accessible, and worthy of being selected.

3. Measure branded demand in Search Console

Search Console's Performance report can separate branded and non-branded queries for eligible properties. The branded filter includes queries containing the brand name, domain, brand-specific products or services, common misspellings, and variations. Google notes that the classification can be wrong and that the filter may be unavailable for low-impression sites or sub-properties.

If the filter is unavailable or clearly misses a variation, open Performance > Search results > + Add filter > Queries > Custom (regex) > Matches regex. Search Console uses RE2 syntax. Matching is case-insensitive and partial by default, so group alternatives with parentheses, separate them with |, and escape a literal dot in a domain. Keep the expression in the audit so future exports use the same definition.

(floxolab|floxo lab|floxolab\.com|stepan nikonov)

Inspect the resulting query rows for false positives and missed variants before saving the definition. For each branded query family, review impressions, clicks, CTR, countries, devices, and the Pages tab. Search Console assigns much of its data to canonical URLs and omits anonymized queries when a query filter is active. A filtered total therefore cannot be compared directly with the unfiltered total and is not a complete count of all brand searches. Use it for trends and unexpected page selection, not as an exact market-size estimate.

If several owned pages appear for one query, decide whether they serve distinct tasks. The homepage may answer the exact brand query while a login, support, location, pricing, or review page answers a modifier. Unexpected pages, hacked query terms, obsolete campaign URLs, or a sharp branded CTR change deserve investigation. The broader Search Console pre-audit covers non-branded demand and indexing checks beyond this audit.

4. Fix the official website result and sitelinks

Check the homepage result first. The title should identify the real brand and useful category without a chain of slogans. The description should describe the business accurately, although Google may generate a different snippet. The displayed site name, favicon, canonical URL, HTTPS version, and destination should all make the official result obvious.

Test the pages a customer is likely to seek after the brand query: contact, services, locations, pricing, support, login, about, team, and reviews or case evidence. Important pages should be linked through a logical navigation structure and use concise, descriptive titles, headings, and internal anchor text.

Google generates sitelinks automatically. There is no control panel where a business chooses the exact links. Google's guidance is to improve page titles, headings, site structure, internal links, and anchor text. If a page should never appear, fix the underlying publication decision. Remove it, restrict it, or use noindex when appropriate. Do not hide useful pages merely because a sitelink is imperfect.

Do not add FAQ or HowTo sections or markup merely to influence sitelinks. Google does not list either as a sitelink control. It has also deprecated HowTo rich results and limited FAQ rich results largely to well-known government and health sites.

Look for other owned URLs that compete with the official version: HTTP copies, staging hosts, old domains, duplicate homepages, parameter URLs, PDFs, outdated profiles, and acquired microsites. Choose the correct canonical destination, redirect true replacements, and remove forgotten public assets that expose stale facts or sensitive material.

5. Align the entity facts across owned assets

Create one reference row for the facts the business can defend publicly. Compare them with the homepage, About page, Contact page, Business Profile, location pages, major social profiles, marketplace accounts, and relevant directories.

primary public name and legitimate alternate name;
official canonical website URL;
logo and recognizable image;
business category and concise description;
public phone, email, address, service area, and hours where applicable;
founder, organization, brand, and location relationships;
official social and platform profiles;
support, booking, login, and contact destinations.

Consistency does not mean forcing the same paragraph everywhere. It means the identity and relationships do not contradict each other. A registered legal name may differ from the public brand. A location may need its own phone and hours. Record those relationships instead of flattening them.

Google says Organization structured data on the homepage can help it understand administrative details and disambiguate an organization. Use the most specific applicable organization subtype, a stable url, name, legitimate alternateName, crawlable logo, and verified profile URLs in sameAs. Markup supports visible evidence. It does not force a knowledge panel or replace accurate page content.

For an established brand, check public pages that already and accurately describe the same organization, such as its official LinkedIn company page, a relevant review profile, or a legitimate company-directory record. Wikidata or Crunchbase can be checked when a real record already exists, but do not create or edit entries merely to populate sameAs. Link only to pages that identify the same entity and add useful public information.

6. Separate Business Profiles from knowledge panels

An eligible local business should claim and maintain its Google Business Profile. That profile can carry address or service area, hours, contact details, photos, links, and customer reviews. Google also derives profile information from public web pages, licensed sources, user contributions, and its own interactions with a place, so review Google updates rather than assuming every field came from the owner.

A knowledge panel for a person, organization, or other entity is a different product. Google says knowledge panels are generated automatically when enough public information is available. Eligible representatives may claim a panel and suggest edits. Local businesses should manage the Business Profile instead of treating a similar-looking panel as interchangeable.

When a panel is inaccurate, record the exact field, current value, correct value, and public URL supporting the correction. Submit one evidence-backed suggestion per issue. A verified representative's feedback may receive priority, but Google still checks suggestions against public information and may decline a change it cannot confirm.

For a single local business, use the local SEO baseline to correct the profile and customer-facing details. For several branches, use the multi-location operating guide so one brand audit does not overwrite real location differences.

7. Triage reviews without trying to erase criticism

Record the review surfaces that actually appear for brand queries: Google, relevant marketplaces, industry platforms, or independent directories. Note whether the profile is claimed, the displayed rating and volume, recent themes, response coverage, duplicate pages, wrong branch mapping, and any policy concern.

A low rating is a business and reputation signal, not automatic evidence of manipulation. Build the review management process for requests, monitoring, ownership, replies, and operational learning. When one serious complaint appears, use the negative review response workflow for privacy, escalation, reporting, and recovery.

Report a review only when it matches a platform policy category. Do not buy positive reviews, pressure customers to change a rating, threaten reviewers, or flood the same surface with templated replies. A defensible public response and a corrected service process are more useful than an unsuccessful attempt to suppress ordinary criticism.

8. Choose the correct path for unwanted results

Result problem	First action	Search follow-up
Outdated owned page	Update, redirect, remove, restrict, or noindex it based on the page's real purpose	Request recrawl; use temporary removal only when urgent and eligible
Old snippet for content already removed from a third-party page	Confirm the live page changed	Use Refresh Outdated Content if its criteria are met
Wrong fact on a live third-party page	Ask the publisher to correct it with evidence	Outdated-content tools are not for a live disagreement
Impersonation, phishing, hacked page, or exposed personal data	Preserve evidence and use the relevant security, platform, privacy, or legal route	Use Search removal routes only when their specific criteria apply
Accurate negative review or commentary	Investigate, respond safely where appropriate, and fix the underlying issue	Publish useful evidence over time; do not promise deletion

Search Console's Removals tool temporarily blocks eligible URLs on a property you own. Google states that the tool alone is not a permanent removal and does not remove content from the internet. Make the permanent page-level change as well. The Refresh Outdated Content tool is for a page or image that no longer exists or has materially removed the shown content. It is not a tool for suppressing a current page merely because the business considers it wrong or unfavorable.

Prioritize by harm, reach, control, and evidence. A phishing page or exposed private data is urgent. A wrong phone number on a prominent profile is high impact and easy to correct. A harmless old directory on page two may be monitor-only. Do not let an emotionally uncomfortable result consume the entire audit while obvious customer-routing errors remain unfixed.

Keep AI answers as a separate surface

Brand SERPs and AI-generated answers are separate surfaces. A clean Google result does not guarantee that ChatGPT, Gemini, or another answer engine identifies the brand, describes it accurately, or cites its official pages. Record AI answers in a separate audit so prompt selection, citations, competitor appearances, and source gaps do not distort this classic brand SERP workflow.

Build a 30-day correction queue

Day 0: preserve evidence for security, privacy, impersonation, or legal issues. Secure compromised owned accounts and pages before editing public copy.

Days 1 to 7: fix wrong owned facts, titles, redirects, indexation decisions, profile access, contact routes, and duplicate owned assets. Submit evidence-backed profile or panel corrections.

Days 8 to 21: improve weak task pages, navigation, internal links, Organization markup, profile completeness, and review ownership. Contact third-party publishers about verifiable factual errors.

Days 22 to 30: repeat the same query set and environment samples. Compare result composition, owned-page CTR, profile accuracy, open corrections, review incidents, and customer-routing failures. Keep unresolved items in a dated queue with an owner and next evidence check.

Measure outcomes, not page-one occupancy

Branded demand: branded impressions and query families over a consistent period.
Owned-result selection: clicks and CTR for the correct official pages, with position and device context.
Routing accuracy: correct c

Backlink Audit for Small Businesses: Keep, Ignore, Investigate

Fri, 11 Sep 2026 15:50:00 +0000

Direct answer: export your backlinks, group them by referring domain and target page, inspect the source and link context, then classify each pattern as keep, ignore, investigate, reclaim, or remove. Do not disavow a link merely because a tool calls it toxic. For most small sites, random irrelevant links are noise, and Google says most sites do not need the Disavow tool.

This guide diagnoses links that already point to a small-business website: referring domains, anchors, linked pages, lost links, suspicious patterns, and the evidence needed for the next action. It does not teach link acquisition, guest-post outreach, digital PR, or campaign prospecting. It also does not review a backlink platform. Tool selection stays secondary to the audit method.

Google still uses link analysis systems, including PageRank, to understand pages and their usefulness. It also uses automated systems to neutralize unnatural links. A responsible audit therefore has two jobs: preserve useful evidence and find patterns that require a real correction. It is not a ritual purge of every unfamiliar domain.

1. Define the scope and evidence threshold

Choose a repeatable audit scope before opening a tool. Record the property, export date, source, known campaigns, site migrations, acquired domains, and the period you can compare. If an agency or contractor previously built links, collect its placement lists, invoices, outreach records, and old disavow file. Those records can explain a pattern that a domain metric cannot.

Use factual states instead of one blended score:

Status	Meaning	Default action
Keep	A legitimate page links in a relevant or editorial context	Record it and protect the destination
Ignore	The link is irrelevant, scraped, duplicated, or low-value without evidence of manipulation	No action; monitor only if the pattern grows
Investigate	Several signals suggest a paid, automated, hacked, or coordinated pattern	Inspect ownership, history, context, and campaign evidence
Reclaim	A useful link was lost or now reaches a broken or wrong destination	Fix your URL path first, then contact the publisher if useful
Remove or qualify	A link you or your provider arranged violates the publisher or search policy	Request removal or an appropriate link attribute and document the attempt

Audit patterns, not feelings. An unfamiliar country, low authority score, foreign language, or ugly domain name can justify a closer look. None proves that the link is harmful or that Google has counted it.

2. Start with Google Search Console, then add another index only when needed

Open Search Console > Links. Review Top linking sites, Top linked pages, and Top linking text. Export both Latest links and More sample links. Google's Links report documentation says the report is a sample, not a comprehensive inventory. Its tables may be truncated, pages are grouped by canonical URL, duplicate links are combined, and the report does not say whether a link is nofollow.

That makes Search Console the free starting point, not a perfect historical database. A commercial crawler may discover links Google does not show, miss links Google found, group domains differently, or record a different first-seen date. A disagreement between tools is normal because each system crawls and stores a different part of the web.

For one small site, Search Console plus a spreadsheet is usually enough for the first audit. Add a paid index when you need recorded new-and-lost history, competitor comparison, recurring alerts, or faster filtering across many domains. The SE Ranking review explains where that platform fits and where a deeper specialist index may be justified. Its backlink monitor can import Search Console links and track status, anchors, targets, and attributes, but any toxicity score remains a triage signal rather than a Google verdict.

3. Normalize the inventory before judging links

Keep the raw exports unchanged and build a working sheet beside them. Normalize protocol, host casing, common tracking parameters, and target URLs without overwriting the evidence. Separate source URL from referring domain because one sitewide template can create thousands of rows while representing one relationship.

source_url
referring_domain
target_url
anchor_text
first_seen
last_seen_or_checked
live_status
link_attribute
source_type
relationship_or_campaign
evidence
classification
next_action
owner
review_date

Do not add a hundred speculative metrics. The useful columns answer four questions: where is the link, where does it lead, why does it exist, and what action is justified? Preserve a notes field for evidence such as an invoice, publisher email, migration map, archived page, or manual-action message.

Deduplicate exact source-to-target pairs, but keep the raw count by domain. A single relevant resource can link to several useful pages. One low-quality template can repeat the same anchor across thousands of URLs. The domain pattern matters more than the headline backlink count.

4. Review referring domains before individual rows

Sort referring domains by number of linking pages, then inspect a sample from the largest domains and every domain connected to a known campaign. A high count can be legitimate, such as a partner directory, documentation site, or press archive. It can also reveal a sitewide footer, syndicated template, scraped mirror, or paid network.

For each domain, check:

whether the linking page is live and publicly reachable;
whether the page has a real audience and coherent purpose;
whether the link is editorial, navigational, sponsored, user-generated, automated, or unexplained;
whether the business, its agency, or a previous owner arranged the placement;
whether the source copies content, publishes unrelated outbound links at scale, or shows signs of compromise;
whether one template repeats the link across many pages;
whether the link still sends relevant referral traffic or customer inquiries, when first-party records are available.

A legitimate niche association with modest metrics may be valuable. A high-scoring domain can still host an irrelevant paid placement. Authority metrics estimate a vendor's view of a domain. They do not replace context, relationship evidence, or Google's policies.

5. Audit target pages and lost links

Group the inventory by target URL. Useful links often expose technical problems before they expose outreach opportunities:

a linked page now returns 404 or soft 404;
a redirect chain ends on a generic homepage instead of the closest replacement;
HTTP, www, parameter, or old-domain variants split the evidence;
an old campaign page remains indexed with stale claims;
a strong resource receives links but has no useful internal route to a relevant service or next task;
important commercial or proof pages have no natural supporting references.

Fix your destination before emailing anyone. Restore a useful missing page, redirect a true replacement directly, remove unnecessary hops, and keep the canonical consistent. The update, merge, redirect, or delete guide helps choose the right page-level action. During a broader domain change, use the site migration checklist so valuable old links reach the correct new URLs.

A lost link is worth reclaiming when the original relationship and destination still make sense. Do not ask a publisher to restore a citation to a page that no longer supports the claim. Improve or replace the source first.

6. Read anchor text as a pattern, not a quota

Group anchors into practical families: brand, URL, person, page title, topical phrase, generic text, image or empty text, and unrelated terms. Natural profiles are messy. A brand may be linked by its name, domain, product, founder, quoted sentence, page title, or an image.

Investigate clusters rather than chasing an ideal percentage. A sudden set of identical commercial anchors across unrelated sites can point to a paid or automated campaign. Unexpected pharmaceutical, gambling, adult, loan, or counterfeit terms can indicate hacked pages, copied content, or malicious spam. Check the source pages and your own site security before assuming the anchors caused a ranking change.

Do not ask legitimate publishers to replace every descriptive anchor with an exact keyword. Google's link guidance recommends concise, descriptive, relevant anchor text. It does not publish a safe branded-to-keyword ratio for backlink profiles.

7. Escalate suspicious patterns with evidence

Google defines link spam as links created primarily to manipulate rankings. Its examples include buying or selling ranking links, excessive exchanges, automated link creation, low-quality directories, keyword-rich widget links, widely distributed footer links, and optimized links in paid articles or press releases. A single weak signal is not enough. Look for a pattern plus a plausible cause.

Observation	Evidence to collect	Likely next step
Random scraper or irrelevant directory	Source sample, growth pattern, no business relationship	Usually ignore
Sitewide exact-match anchors	Template locations, ownership, placement agreement, link attributes	Investigate and request correction if arranged
Old paid-post campaign	Invoices, placement list, anchor pattern, current link attributes	Request removal or qualification; document failures
Lost editorial citation	Archived source, old target, current replacement, relevance	Fix destination, then request an update if warranted
Unnatural-links manual action	Search Console notice, affected scope, campaign records, removal log	Follow the manual-action process and prepare a documented review request

Check Search Console > Security & Manual Actions > Manual actions. If the report shows a green check, do not invent a manual action from a traffic decline or third-party score. Rankings can change for many reasons. The backlink audit should produce evidence, not a retrospective story built around one chart.

8. Use Disavow only after crossing Google's threshold

Google describes the Disavow tool as an advanced feature that can harm search performance when used incorrectly. It says to disavow only when both conditions are true: a considerable number of spammy, artificial, or low-quality links point to the site, and those links caused a manual action or are likely to cause one. Most sites do not need the tool.

If your business or its provider created a violating campaign, first try to remove the links or ask the publisher to prevent them from passing ranking credit. Keep the request, response, and result. For a manual action, Google's instructions require fixing the full issue, documenting the outcome, and then requesting review. A screenshot of a toxicity score is not a cleanup record.

If the threshold is met, preserve the current disavow list before editing it. Uploading a new file replaces the old list for that property. Use one URL or one domain: entry per line, add comments beginning with #, and never include a domain you have not manually checked.

# Paid directory campaign commissioned in 2024.
# Removal requested 2026-08-08; publisher did not respond.
domain:example-spam.test
https://example.test/paid-placement.html

Disavowed links can remain visible in the Links report, and processing can take weeks as Google recrawls and reprocesses them. Do not repeatedly replace the file while waiting. Escalate a high-risk case to an experienced SEO or legal adviser when ownership, extortion, defamation, or contractual disputes are involved.

Build a recurring review that a small team can maintain

For a stable small site, a quarterly review is often enough. Review monthly during a migration, active PR or partnership work, a cleanup, or a suspicious spike. The owner should compare the same exports and record only meaningful changes.

Check alerts first. Review Search Console manual actions and security issues before interpreting tool scores.
Export and archive. Save dated raw files from Search Console and any paid index in use.
Compare domains and targets. Find new clusters, lost useful links, broken destinations, and unexpected anchors.
Sample manually. Open the source, verify context, and record the relationship or likely cause.
Fix owned problems. Repair destinations, redirects, canonicals, security issues, and outdated assets.
Escalate only with evidence. Separate harmless noise from arranged or coordinated violations.
Validate the queue. Recheck live status, publisher changes, manual-action state, and affected targets on the next review date.

What not to do

Do not disavow every low-score domain. Vendor metrics are triage aids, not Google decisions.
Do not treat Search Console as a complete link database. Its report is a sample with grouping and export limits.
Do not compare raw backlink counts across tools. Compare patterns inside a consistent source and time window.
Do not email every unfamiliar publisher. Removal outreach can waste time or attract exploitative replies when the link is harmless noise.
Do not repair a lost link before checking the destination. The old page may no longer deserve the citation.
Do not diagnose a manual action from a ranking drop. Check the actual Search Console report.
Do not overwrite an old disavow file without preserving it. A new upload replaces the existing list for that property.
Do not turn the audit into a link-building campaign. Diagnosis and acquisition require different evidence, priorities, and risk controls.

Verification checklist

The audit records its property, date, sources, known campaigns, and comparison window.
Raw exports are preserved separately from the normalized working sheet.
Referring domains, source URLs, target URLs, anchors, and live status are not collapsed into one score.
Large domain clusters and known campaigns received manual samples.
Broken targets, redirects, canonicals, and migration paths were checked before outreach.
Suspicious anchors were assessed as patterns and traced to a plausible cause.
The Manual actions and Security issues reports were checked directly.
Removal or qualification requests are documented only for links with a defensible reason.
Disavow is avoided unless Google's high threshold is met.
Every open item has evidence, an owner, a next action, and a review date.

A useful backlink audit makes the profile less mysterious. Keep legitimate references, ignore ordinary web noise, recover valuable links when the destination still deserves them, investigate coordinated patterns, and reserve removal or Disavow for evidence-backed risk. The output is an action queue, not a fear score.

After the audit, acquisition becomes a separate decision. If the business is choosing between a newsworthy evidence campaign and an expert contribution, use the digital PR versus guest posting comparison to evaluate control, cost, speed, risk, and audience fit before commissioning placements.

Sources checked

Google's Links report, l

Google Rankings Aren’t the Whole Story Anymore: SEO in the Age of AI Search

Wed, 09 Sep 2026 08:03:47 +0000

🚀 Google Rankings Aren’t the Whole Story Anymore: SEO in the Age of AI Search

You rank on Google. Great. But are people actually finding you?

For years, SEO had a familiar goal:

Get higher on Google.

Page 10 → Page 3 → Page 1 → Position #1 🎯

But search is changing.

Today, people discover information through traditional search engines, AI-generated answers, AI Overviews, conversational search, and other discovery experiences.

And that creates an important question:

Is a Google ranking alone enough to understand your real search visibility?

Probably not.

Welcome to SEO in the age of AI search.

🤔 A Quick SEO Challenge

Imagine this:

Your website ranks #3 on Google for an important keyword.

Sounds great.

But then you notice:

📈 Impressions are increasing
🖱️ Clicks are staying flat
🤖 AI-generated answers appear prominently
👀 Competitors appear across more search experiences
📉 Your organic traffic barely changes

Is ranking #3 still a success?

Yes — but it doesn't tell the whole story.

Modern SEO requires us to look beyond a single position number.

🔍 The Search Journey Is Changing

Traditional Search

User searches
↓
Google results
↓
User clicks a website
↓
User finds the answer

AI-Assisted Search

User asks a question
↓
Search engine / AI system
↓
Generated answer or summary
↓
Sources, recommendations and links
↓
Maybe a website click

Notice the important word?

Maybe.

Users can sometimes get the information they need directly from the search experience.

That means the way we measure SEO success needs to evolve too.

🧠 Ask a Better SEO Question

Instead of asking only:

“What position am I ranking?”

Start asking:

“How visible is my website or brand wherever my audience is searching?”

That's a much bigger question.

And it changes what we need to monitor.

📊 5 SEO Signals Worth Watching

1️⃣ Keyword Rankings

Rankings still matter.

But don't look only at today's position.

Look at the movement.

Day	Position
Monday	#18
Tuesday	#15
Wednesday	#11
Thursday	#8
Friday	#6 🚀

The trend tells you much more than simply seeing:

Current position: #6

2️⃣ Search Impressions

A good ranking doesn't automatically mean strong visibility.

Search impressions help answer:

How often is my website actually appearing in search?

For example:

Metric	Last Month	This Month
Average Position	8.1	5.4
Impressions	12,400	18,900
Clicks	820	790

Interesting, isn't it?

Your ranking improved. ✅

Your impressions increased. ✅

But your clicks dropped. ⚠️

That's something worth investigating.

3️⃣ Click-Through Rate

Now consider two pages:

Page	Position	Impressions	CTR
Page A	#2	20,000	1.8%
Page B	#5	12,000	5.7%

Which page is performing better?

There isn't always a simple answer.

CTR can be influenced by:

Search intent
Page title
Search snippet
Brand recognition
Competing results
SERP features
AI-generated answers

So remember:

Ranking ≠ Complete Performance

4️⃣ Backlinks & Authority

Search visibility isn't only about keywords.

Quality backlinks can help search engines understand that other websites consider your content useful or authoritative.

Ask yourself:

Who is linking to my website?
Are those links relevant?
Are important backlinks disappearing?
Which pages attract the most links?
Are competitors earning links that I'm missing?

5️⃣ Technical SEO Health

Great content can still struggle if your website has technical problems.

Keep an eye on:

🔎 Crawlability
📑 Indexing
🔗 Broken links
🏷️ Metadata
🧱 Page structure
📱 Mobile usability
⚡ Performance
🔁 Canonical issues

Your content can't perform well if search engines struggle to access or understand it.

🎯 30-Second SEO Health Check

Can you answer these questions about your website right now?

[ ] What are my highest-ranking keywords?
[ ] Which keywords improved this week?
[ ] Which keywords dropped?
[ ] Which pages receive the most impressions?
[ ] Which pages have poor CTR?
[ ] Are there technical SEO problems?
[ ] Which websites link to me?
[ ] Does performance change by country?
[ ] Am I checking more than one search engine?
[ ] Can I see important SEO changes without jumping between several tools?

What's your score?

8–10 → 🟢 Strong visibility monitoring

5–7 → 🟡 Good start, but there may be gaps

0–4 → 🔴 Your website may be telling you a story you're not currently seeing.

🌍 Google Isn't the Entire Search Ecosystem

Google is hugely important.

But your audience doesn't necessarily exist in only one search environment.

Depending on the country and audience, discovery can happen through:

Google
Bing
DuckDuckGo
Yahoo
Baidu
Yandex
AI-powered search experiences

This is why looking at:

Keyword + Country + Search Engine + Performance

can provide a better picture than looking at one global ranking number.

🤖 And Then Came AI Search

This is where things get particularly interesting.

Search engines are increasingly trying to answer questions, rather than simply return a list of links.

Someone might search:

“How can I improve technical SEO for a small business website?”

Traditionally, the user would choose a result and visit the website.

Now, they may first encounter an AI-generated answer or summary.

That means websites are increasingly competing for more than:

Position #1

They're competing for:

👀 Visibility
🧠 Authority
🎯 Relevance
🤝 Trust
💬 Mentions
📚 Useful content
🖱️ Clicks

💡 So What Should Website Owners Do?

Don't abandon traditional SEO.

The fundamentals still matter.

✅ Create genuinely useful content

Answer the question the visitor actually has.

Not what you think Google wants.

✅ Maintain strong technical SEO

Make it easy for search engines to:

Crawl → Understand → Index → Rank

your content.

✅ Build topical authority

Don't publish 50 unrelated articles simply because keywords have search volume.

Build useful depth around subjects connected to your business.

✅ Earn trustworthy signals

Relevant backlinks, references and brand mentions can strengthen your presence.

✅ Monitor what changes

SEO isn't:

Optimize → Done ❌

It's:

Measure → Understand → Improve → Monitor → Repeat 🔄

🛠️ Why We Built DevnDespro SEO

While working with websites, we kept seeing the same challenge:

SEO information is scattered across different places.

Rankings in one place.

Search Console somewhere else.

Backlinks somewhere else.

Technical issues somewhere else.

Reports somewhere else.

That led us to build DevnDespro SEO around a simple idea:

Make everyday SEO monitoring easier to access and understand.

With DevnDespro SEO, we're bringing important SEO workflows closer together.

🔎 Keyword Monitoring

Track the keywords that actually matter to your website.

📈 Ranking Insights

See where your keywords stand and monitor changes over time.

🌍 Country-Based Tracking

Search visibility isn't identical everywhere.

Track rankings with location in mind.

🔍 Multiple Search Engines

Go beyond a Google-only view of SEO.

📊 Google Search Console Insights

Understand impressions, clicks and search performance.

🔗 Backlink Information

Keep an eye on the websites connecting to yours.

🩺 SEO / Website Auditing

Identify problems that could be holding your website back.

📑 Reports

Bring important SEO information together in a clearer format.

💻 At Your Desk. 📱 On the Move.

SEO problems don't politely wait until you're sitting in front of your laptop.

Maybe you published a new page yesterday.

Maybe an important keyword suddenly moved.

Maybe you're travelling and simply want to check your project.

That's why DevnDespro SEO is available on both Web and Android.

💻 DevnDespro SEO Web

Use the web application when you want a broader view of your SEO projects, rankings, backlinks, reports and website insights.

👉 Explore DevnDespro SEO

https://www.devndespro.com/

📱 DevnDespro SEO for Android

Want to check SEO without opening your laptop?

Take your SEO monitoring with you.

👉 Get DevnDespro SEO on Google Play

https://play.google.com/store/apps/details?id=com.devndespro.seo

🧪 Try This With Your Own Website

Choose five keywords that matter to your business.

Fill in this simple table:

Keyword	Current Rank	Country	Search Engine	Landing Page
Keyword 1	?	?	?	?
Keyword 2	?	?	?	?
Keyword 3	?	?	?	?
Keyword 4	?	?	?	?
Keyword 5	?	?	?	?

Check them again next week.

But don't only ask:

“Did I reach #1?”

Ask:

“What changed — and why?”

That's where useful SEO analysis begins.

🔮 The Future Isn't “SEO vs AI”

It's tempting to frame the conversation as:

Traditional SEO is dying. AI search is replacing it.

But the reality is more interesting.

People will continue searching for:

Answers
Products
Businesses
Comparisons
Recommendations
Tutorials
Services
Trusted information

What changes is how those answers are discovered and presented.

And that means SEO isn't disappearing.

SEO is evolving.

🚀 One Question to Take Away

For years, SEO conversations started with:

“Where do I rank on Google?”

In the age of AI search, there's a bigger question:

“When someone searches for what I offer, where — and how — does my brand appear?”

That's the visibility worth understanding.

👋 Your Turn

What are you paying the most attention to right now?

Google rankings?
Organic traffic?
Click-through rate?
Backlinks?
AI-search visibility?

SEO is changing quickly.

The interesting part is learning what to measure next.

🚀 Explore DevnDespro SEO

🌐 Web Application
https://www.devndespro.com/

📱 Android Application
https://play.google.com/store/apps/details?id=com.devndespro.seo

Track. Understand. Improve. Wherever you work.

DevnDespro SEO is continuously evolving. Available features and supported data sources may change as the platform develops.