Search optimisation is not a way to make generic prose rank. It is the work of understanding a searcher’s task, publishing the most useful answer you can support and making that answer easy for people and search systems to find.

Google’s own guidance asks whether content provides original information, substantial value, clear sourcing and first-hand expertise — and warns against producing many pages mainly to attract search traffic. Read Creating helpful, reliable, people-first content and the SEO Starter Guide.

Build a search map from real work

Collect questions from sales calls, support, community discussions, course assignments and your own search results. Group them by job:

  • Learn: “how to price an online course” or “improve course completion”.
  • Compare: “Kajabi alternatives”, “Skool vs Circle” or “best course platform for community”.
  • Do: “resize a course thumbnail”, “calculate membership churn” or “write a course outline”.
  • Decide: “what does a course platform cost?” or “course or community first?”.
  • Operate: consent, VAT, refunds, email authentication and migration.

One good page should own one primary job and cover the necessary subquestions. Do not split tiny wording variations into near-duplicate articles.

Choose the best format for the task

Use an article when explanation and judgement matter. Use a comparison when current facts and trade-offs matter. Use a calculator, checklist or browser tool when the visitor needs an output. Use product documentation when the answer is about operating your product.

Free tools can attract links because they remain useful after the article is read. The tool must solve the task without unnecessary login, especially when the computation can stay in the browser. Offer an optional email follow-up after the result, with a clear promise, rather than holding the result hostage.

Add evidence competitors cannot cheaply copy

Useful differentiation includes:

  • a method tested in your own course or creator operation;
  • a downloadable template used in real work;
  • dated prices linked to each vendor’s official page;
  • a calculator whose assumptions are visible;
  • product screenshots from the current interface;
  • Swedish legal or tax sources with clear limitations;
  • interviews that preserve disagreement and context.

Never turn one customer, one experiment or an old report into a universal statistic. Show dates, definitions and limitations close to the claim.

Make the page technically understandable

Give every page a descriptive title, one clear H1, a readable URL and useful internal links. Provide a canonical URL and correct language alternates for translated pages. Include structured data only when the visible content meets that schema; markup does not create eligibility from thin content.

Use descriptive link text, accessible images and fast pages. Google’s current Core Web Vitals guidance uses LCP within 2.5 seconds, INP below 200 ms and CLS below 0.1 at the 75th percentile (documentation). These are experience thresholds, not a ranking guarantee.

Publish as a maintained library

For volatile articles — prices, platform comparisons, law and product capabilities — store a verification date and source list. Schedule review. Redirect old URLs when titles change. Keep a useful older page updated instead of publishing a second near-duplicate “2027” version unless the search job genuinely changes.

Let Search Console choose the next revision

After indexing, review:

  • queries with impressions but weak alignment to the page;
  • pages ranking for a question they only answer briefly;
  • country and device differences;
  • clicks lost after a title or URL change;
  • index and canonical issues.

Search Console reports Google Search performance, not all demand. Combine it with on-site search, analytics, support questions and interviews. Revise the page to answer the observed task better; do not stuff every accidental query into the copy.

Idun Blue’s own resource library follows this approach: current comparisons, free local calculators and product help separated by purpose. The platform is in internal beta; join the waitlist if you want to follow the product as external onboarding opens.