Visibility
Search Console does not rank a profile. It watches the canonical URL at /u/slug
The Business panel connects Search Console read-only, finds the property that covers https://linkforge.me/u/slug, and reads pages from the last 28 days. It sends nothing to the indexing API.
Search Console is a reading tool. For a property you have verified at Google, it says which URLs had impressions and clicks. It does not “rank” an Instagram account. It does not guess that your widget is your site. If the property you verified is a domain, or a prefix, the URL inside it still has to be the document’s URL. On LinkForge that document has a canonical address: https://linkforge.me/u/{slug}. Connecting the Console to something else, then wondering why the page does not appear, is the most common mistake of creators who finally have an HTML page.
The panel is on the Business plan, at €26 a month, under Visibility. Pro at €7 a month publishes the page, the domain, Studio, the title and the meta. It does not open this reading. Free already publishes the document. Agency is not subscribable. The tiers are on pricing.
The URL that matters is the canonical
The page emits its canonical to https://linkforge.me/u/{slug}. Open Graph, the llms.txt link when Pro leaves it public, the JSON-LD: the same address. A domain in your name, included in Pro, is another door to this page. It does not create a second document. If you verify only the domain in Search Console, the reading is useful only when that property also covers the canonical URL — a sc-domain: property can, a prefix that is too narrow cannot.
The useful gesture is therefore: know the exact URL, put it in the bios and on the QR code, and ask the Console whether this URL, not the social profile, has been seen. Inspecting a screenshot does nothing. Inspecting https://linkforge.me/u/your-slug speaks to the document described in the HTML robots can quote.
What the connection is allowed to do
The connect button, when Google credentials are in place on the service, sends you to Google’s consent with read-only access to Search Console. Read-only: LinkForge does not submit a URL to the indexing API, does not remove pages, does not edit your sitemap with this token. The refresh token is encrypted. It is not shown in the panel. Without encryption configured on the service, the connection does not finish: a clear failure is better than a token in clear.
Google returns a refresh token only if offline access is granted. The flow asks for it. If you already accepted the app without that access, you sometimes have to remove the authorisation in the Google account and start again. Without that token, the connection cannot reread the Console later. The callback stops there, rather than pretending everything is wired.
Once the account is linked, the intended read lists the properties you can access. It keeps the one that covers the public URL: a prefix the public address continues, or a domain property whose host matches. If several properties could match, the most specific wins. If there is none, the recommendation is to verify the property, and the text contains the URL. Nobody invents a property for you.
Twenty-eight days, by page
When a property matches, the read asks for pages from the last twenty-eight days: the URL, impressions, clicks. The row cap is short, on purpose. You do not get an agency export. You get enough to see whether the canonical URL appears, and which other URLs of the same property Google has already shown.
If the canonical URL is not in the rows, it is noted with no data, and a recommendation says so: no impressions yet. Zero is not a bug in the panel. It is the normal state of a young page, an empty page, or a page Google has not chosen to show. The panel does not turn that zero into a promise of a deadline.
If the call to Google fails, the recommendation speaks of coverage being unavailable. It does not manufacture replacement numbers. A table of invented zeros would be worse than a gap: you would rewrite a title on a fiction.
When Google credentials are not configured on the deployment, the same button does not open a fake Console. It records a demonstration mode: the public URL, a “submitted” state, and recommendations — a distinct title if one is missing, inspect this URL, keep HTML. There are no simulated clicks. The day a real read is possible, the numbers come from Google or they do not exist.
The recommendations, and what they do not do
They are short, and they talk about the page, not about a score.
A title. If there is neither a page title nor an SEO title, the recommendation says so. “Links” or “Welcome” does not help a person reading a result. The craft and, if it matters, the city, fit on one line.
The vitrine. If the modules are not assembled, the recommendation reminds you that a page of text is easier to quote than a list of buttons. Assembling is a choice, described in from a bio link to a vitrine. An empty vitrine does not tick that box by magic.
Inspection. The recommendation contains the public URL. That is the one you paste into Google’s inspection tool, once the property is verified. LinkForge does not click “request indexing” for you. The token’s scope does not allow it. You do it if you decide to, on the right URL.
HTML. The recommendation reminds you that the vitrine stays text in the page. A price that exists only inside an image will not be the sentence the Console associates with the URL.
None of these lines changes Google. They change what you will fix in the dashboard: the title, the modules, the URL you share. Then you run the read again. Impressions, if they come, come from real searches, often late. A page fixed on Monday does not have a history on Monday evening.
What not to verify instead
The Instagram profile. The TikTok preview. A shortener. A Notion page that is not canonical. Each can be a property, or a tool. None of them is the document whose canonical is /u/{slug}. If your impressions live on an old URL, you are measuring the old URL. Put the canonical in the bio, remove the intermediate hop, and give the new address time to have rows of its own.
The custom domain deserves its own sentence. If it serves the same page and the canonical remains linkforge.me/u/{slug}, that URL is the one you want to see in the rows. A property that contains only www.your-name.fr can show doors and never the canonical, if the two are not the same thing to Google. Look at the canonical tag in the source before you choose the property. Then verify the one that covers that tag.
Leads and clicks in the LinkForge dashboard are another measurement: visits on the page, form sends. Search Console measures Google search. The two can disagree without either being broken. Many visits from a story, zero impressions: the page is alive, search has not shown it yet. The reverse exists too. Do not mix the two columns in the same sentence when you decide to rewrite a title.
A short sequence
Publish the page, with a title that says the craft. Open the source, copy the canonical. At Google, verify a property that covers that URL. In Visibility, connect the Console. Read whether the URL is there, and with what impressions over twenty-eight days. If there is no property, verify it. If there are no impressions, improve the text — the bio, the services — rather than clicking “index” ten times. The indexing request, if you make it, happens in Google’s interface, on this URL, once. Then you wait for searches, not for a score.
The page is created before the Console: open an account. The Console is connected when Business is there, and when there is a document to watch. Watching an empty page produces a very reliable zero.
FAQ
Is Search Console included in Pro?
No. The connection and the read are part of Business, at €26 a month. Pro at €7 a month publishes the page, the domain and the SEO fields. The document exists before the Console.
Can LinkForge force indexation?
No. The token is read-only. It does not submit the URL to the indexing API. You can inspect https://linkforge.me/u/{slug} yourself in Search Console, once the property is verified.
What data is read?
The properties your Google account can access, then pages from the last twenty-eight days on the property that covers the public URL: impressions and clicks. If there is no compatible property, the recommendation is to verify one. Numbers are not invented.
What if the Google connection is not configured on the service?
The button records a demonstration mode: the public URL and recommendations about the title, inspection and HTML. It does not show fake clicks.
Should I verify the domain or the /u/slug URL?
Verify a property that covers the canonical the page emits, https://linkforge.me/u/{slug}. A domain is enough only if it really covers that URL. Look at the canonical tag before you choose.
Create my page — Pro is 7€/month (~$7)
Free to start. Pro is 7€/month (~$7 depending on exchange) for a custom domain and full SEO controls.