What changed in Contextter
A dated record of product changes, workflow improvements, fixes, and the occasional update that changes existing behavior.
Public search discovery now focuses on core product pages
Contextter's public navigation and search discovery now put the homepage, Platform and Solutions first. Comparison and alternative pages are no longer published, and secondary Tools and Resources pages no longer compete for space in the global navigation. The XML sitemap also excludes legal and utility routes. Blog category, tag and author archives enter search discovery only when at least three published articles support the archive, while each published article remains available on its own URL.
Connected agents can request bounded fresh SEO work
Connected agents can now request approval for fresh keyword research, keyword metrics, competitor research, AI visibility, domain snapshots, and site audits. Each request names the exact capability and includes a maximum charge in EUR. Nothing runs automatically. Access remains tied to the Organization, Workspace, connected client, and owner. Before paid work starts, Contextter reserves the approved maximum from EUR Balance. It then settles the actual cost or releases the unused amount.
Public website now focuses on English and German
Contextter's public website now supports English and German. The language switcher and HTML sitemap show only those two languages. Former French and Spanish URLs permanently redirect to the same English path instead of returning errors or remaining as separate pages. Existing translation data remains in the codebase. French or Spanish will return publicly only when Contextter can maintain the product experience and content quality in that language.
Public pages now declare their language in the HTML
Contextter's public pages now declare the active language in the server-rendered HTML. English pages use `en`, and German pages use `de`. Browsers, assistive technology, and crawlers can now identify localized content before client-side code runs. Canonical URLs and language alternatives remain unchanged.
Connected agents can check their approved access reliably
Connected agents can now list the authorization grants for their selected Workspace even when no grant exists yet. An empty list is returned as a valid state instead of interrupting the connection. The request remains bound to the Organization, Workspace, connected client, and owner. Read limits still apply, while checking grant status does not reserve EUR Balance or start paid SEO work.
Core SEO workspaces now share one clearer reading order
Dashboard, Action Center, Domain Overview, Keyword Research, Keyword Database, Position Tracking, Site Audit, and Activity now follow the same reading order: current state, supporting evidence or change, the next useful action, and how to verify the result. The underlying metrics, charts, filters, tables, and specialist views remain available. Long reports use the page as their vertical reading flow instead of splitting the work across several small scroll areas. Wide tables and module tabs remain horizontally reachable on narrow screens. Loading, empty, partial, stale, failed, and not-yet-measured states stay distinct where the available evidence supports them. Action Center and Position Tracking also keep their relevant view, scope, filter, and detail context in the URL. Shared links and browser navigation can therefore return to the same working context instead of reopening a generic overview.
Each product page now names the SEO tool it provides
The homepage now presents Contextter as on-demand SEO software that does not require a subscription. It explains the free organizing and export workflow, then separates that work from fresh data requested only when needed. Platform, Keyword Database, Site Audit, and the seven feature pages now name their own product category in the main heading and search metadata. Decorative sample queries in the homepage hero are painted visually instead of appearing as page-copy text nodes. Each homepage chapter now links to the relevant product or solution page. A new evidence section also explains paid-action scope, data freshness, and the limits of later comparisons. Localized pages set the active document language without giving up static rendering.
Workspace analyses stay compact and show the data already available
Domain Overview and Competitive Research now use the available viewport height consistently. Competitor lists stop growing after their maximum height and scroll inside their panel, while the associated maps and charts use the remaining space. Site Audit now keeps one intentional content scroll region across its dense views. Click-depth and issue-category summaries are more compact, labels remain readable, and charts no longer force adjacent cards to stretch. Position Tracking shows saved ranking history even when the newest scheduled run could not start, and reports that run status accurately. Starting Keyword Research keeps the active state lightweight instead of loading result datasets before they exist.
Main marketing pages now state their search intent clearly
The homepage now identifies Contextter as an AI-assisted SEO platform for keyword research, technical Site Audits, prioritization, and measurable SEO workflows. This category statement appears in the first visible section as well as the page metadata. Platform, Features, Keyword Database, Site Audit, Solutions, Pricing, Resources, Learning Center, Tools, and Owned Data now have distinct titles and descriptions that match each page's job. The shorter descriptions improve snippet clarity without promising rankings or traffic.
Agent connections now start with the work, not the protocol
The Agent Platform now opens with a guided MCP connection for Codex, Claude, Visual Studio Code, Cursor, and other compatible clients. The selected workspace is built into the connection, OAuth is the standard path, and the technical endpoint and Inspector remain available only when they are needed. The capability view now explains 21 focused SEO tools instead of presenting the much larger internal operation catalog. Keyword research, domain and competitor analysis, Site Audit, tracking, planning, content, publishing, and verification are grouped by the result an agent can deliver. The Developer API has its own advanced area with workspace-scoped access, billing guidance, and an API Explorer. MCP and REST use the same organization EUR Balance, approval policy, spending limits, and settlement controls.
Site Audit examples are now clearly labeled
The public Site Audit overview now identifies its illustrated crawl counts and run history as sample data. The preview remains concrete without looking like a live customer audit. Each example issue family also explains its own impact and verification path. Broken links, missing canonicals, redirect chains, and orphan pages no longer share one generic canonical explanation, and the displayed URLs are explicitly presented as examples.
Billing now separates cash, balance, invoices, and receipts
Billing history now answers two different questions separately: how much cash was paid or refunded, and how much prepaid EUR balance was added or removed. That distinction matters when a plan includes more balance than its purchase price. Older transactions whose paid amount cannot be reconstructed are marked as unavailable instead of being presented as estimates. Completed Polar orders expose the invoice or payment-receipt links Polar returns. If a document link is unavailable, Contextter points to the Polar customer portal rather than creating a second invoice or inventing a receipt. Portal access remains available after a downgrade to Free, so earlier orders, billing addresses, tax details, and payment methods can still be managed there. Before a new subscription or top-up, the buyer identifies the purchase as private or business use. Polar remains the merchant of record and collects the billing and tax details in its checkout. The confirmation explains that Contextter does not offer voluntary refunds for unused subscription time or prepaid balance. Mandatory rights and refunds initiated by Polar remain unaffected. Public cancellation and consumer-withdrawal routes give customers a direct path outside the product navigation. The cancellation form distinguishes ordinary from extraordinary cancellation and asks for the important reason only in the latter case. Both declarations produce an immediate reference and an email confirmation. Signed-in customers can reach Polar cancellation without a feedback survey in between. The public forms and their delivery were browser-verified. Authenticated checkout, document, portal, renewal, refund, cancellation, and withdrawal paths still require controlled production transactions before the entire provider flow can be called live-proven. This release is not a claim of legal or tax adviser approval.
Keyword discovery finds more, remembers paid data, and reaches back to 2019
Deep keyword discovery now combines two complementary expansion methods. A category-based lookup covers all seeds in one request and returns volume, CPC, difficulty, intent, and a 12-month trend with every keyword. Imported candidates therefore arrive with the base metrics already collected. A phrase scan adds up to 300 ideas per seed that contain the seed wording directly. Both methods appear as separate items in the cost preview before a run starts. Discovery also reuses paid data more consistently. Keywords that already carry base metrics from an earlier discovery import count as covered during freshness checks and automatic enrichment after import. The same base dataset is not purchased a second time simply because the keyword entered the workspace through a different route. The keyword dossier adds an optional "History since 2019" package. It extends the 12-month trend into a multi-year monthly series and was introduced at about one cent per keyword, passed through at source cost. The package can be requested for one keyword from its trend section or for a selection in the enrichment dialog. Every discovery row now opens a dossier. A keyword already in the database opens its full workbench view. A candidate that has not been imported opens a compact read-only view with the metrics purchased by the current run, so the evidence is available before the import decision. Automatic base-data enrichment after an import now uses a lower-cost delivery option when the primary source has no record for a keyword. This route costs about one third less than an immediate request and normally returns volume data within a few hours. Interactive enrichment keeps the immediate option when someone is waiting for the result.
The competitor catalog now connects paid data with practical decisions
Each competitor now opens with an overview of its organic footprint: ranking keywords, estimated traffic and value, recent movement, and position distribution. Ranking tables retain the exact URL behind each keyword, while source badges explain why a domain entered the catalog and which query last surfaced it. Existing Domain Overview evidence is reused when available instead of prompting for the same purchase again. Competitive Research now separates overview, catalog, comparison, and statistics. Comparisons show module coverage, collection dates, failures, and a verdict with the proposed next step; incomplete runs open their evidence instead of looking complete. Deeper data loads only for the tab being viewed, which reduces the initial load while keeping traffic history, keyword profiles, link signals, and the market map available when needed.
Domain Overview turns more stored evidence into working views
Domain Overview now turns more stored analysis evidence into working views. Rankings include SERP-feature coverage, volume trends, and position charts; competitors show their ranking profile; pages show traffic concentration; and backlinks add authority, link-position, and referring-domain distributions. History separates estimated traffic growth, keyword movement, ranking shares, and churn. Each chart states its basis and uses bounded server aggregates rather than only the rows visible in the current table. The new Opportunities view identifies promising ranking ranges with a disclosed CTR estimate, brand heuristics, SERP-feature exposure, and relative authority. These are decision signals, not traffic promises or causal claims. Keywords can move into a list or research, competitors can be saved, and Domain Overview can cross-check important pages and linked targets against the latest Site Audit. Pages outside that crawl remain unmatched rather than being labelled healthy.
Sort the Domain Overview rows you have loaded
Domain Overview tables now follow the same interaction pattern. Rows highlight on hover, headers stay visible while you scroll, and a click on a data header sorts the results without adding a separate control bar. Results still arrive in small server pages. Sorting applies only to the rows currently loaded and recalculates when more rows arrive, so it should not be read as a global sort across the full analysis. Top Organic Keywords can now also sort by ranking URL and search intent. Keyword Gap, the complete competitor table, and the Rankings, Pages, Competitors, and Backlinks tabs use the same behavior.
Keyword imports can add missing base data after showing the price
The default pricing policy for keyword enrichment now passes the data cost through without a markup. The quote shown before a run remains the source of truth if that pricing policy changes. It breaks the selected data packages and fallback routes into a visible estimate before any paid work starts. When research results are imported, enrichment is selected by default for the keywords still missing base data. The import dialog estimates that missing scope and lets you turn enrichment off. Keywords that already carry fresh paid metrics are not purchased again. An optional long-tail fallback can ask a second volume source about terms the primary database does not cover, although that source may still return no data. The 12-month histories already returned during research are now stored in the Keyword Database instead of being discarded. When that history is available, trend sparklines can appear as soon as the import finishes.
Activity filters now reconcile the whole view and its export
Filtering Activity by area, status, initiator, cost state, or calendar day now changes the whole view, not just the timeline. Headline figures, the daily chart, the atlas, the category breakdown, and spend per member all recalculate for the same structured scope. Free-text search still refines only the entries already loaded, and the interface labels that narrower behavior. The activity calendar now covers twelve months independently of the shorter analysis window. Daily rollups provide exact calendar totals rather than a sample, with the current day recalculated from live operations. While older history is still being backfilled, the view marks that state and uses a bounded fallback instead of pretending the rollup is complete. Every view can be exported as a CSV file containing the rows currently visible. The file records its own scope, including the window, row count, and creation date. Cost columns are included only for teammates with billing permission. Optimizer and Precision Editor runs recorded after this release now appear as named operations with their own outcome and duration, rather than unattributed usage costs. Earlier runs were not reconstructed retroactively.
Large Site Audit reports no longer reread every link during publication
Current crawls keep exact link counters with each URL. Report publication now reuses those counters instead of loading thousands of link records again. Only older crawls without counters still need that extra read. This avoids the cumulative read limit that could leave a crawl complete while its report stayed unfinished. A completed or partial run remains eligible for automatic recovery until the required publication stages finish. If publication stalls, or report totals are still being calculated, recovery can continue after the run has been idle long enough. There is no age cutoff for this incomplete publication state.
Activity now explains workspace work and settled spend
Activity now brings the work from across your SEO workspace into one history: Domain Overview, Competitive Research, keyword work, Position Tracking, Site Audit, Search Performance, Action Center, Research, Content, and Brain. A workflow appears as one understandable operation, rather than a trail of technical background steps. The redesigned view adds daily activity and spend trends, a calendar heatmap, category development, attention states, source coverage, filters, and an expandable timeline with links back to the product where the work happened. Settled spend can also be broken down by the workspace member who initiated the billed work, including each member's share and daily trend. Only teammates with billing permission receive that breakdown. Everyone else keeps the operational history without cost or contributor data. Selecting a calendar day filters the timeline, and the control for clearing the selection sits beside that date in the calendar header. The timeline covers the latest 100 normalized operations. If a source or reading cap makes a figure partial, the coverage view says so instead of presenting it as a complete total.
Site Audit website setup now follows the current crawl limits
Adding a website to Site Audit no longer fails when an older browser default exceeds the crawl limits currently available to the workspace. New sites now inherit the active limits used when a crawl starts, while existing settings remain compatible. Crawl-depth and URL-count fields can be cleared and entered again without snapping back to their previous value. Their maximum follows the active product limit rather than the site's current selection. Existing website settings now expose the same crawl scope as initial setup, including depth, included and excluded paths, rendering, and robots.txt handling. Saved changes apply to future runs. New audits also recover when the dedicated crawl process loses its connection during startup. Instead of leaving a run at the first seed URL while appearing healthy, Site Audit retries the connection and restarts the failed process if recovery does not succeed within its limit. Monthly run allowances now treat no-result outcomes consistently. Cancelled, failed, and partial crawls return their run slot when fewer than ten pages completed. Completed crawls, and incomplete crawls that produced meaningful page work, still count. Page-based billing remains tied to the pages actually consumed.
AI Crawler Checker now opens every check as a full report
AI Crawler Checker results now open in a dedicated report instead of appearing below the form. Four eligibility verdicts lead the page, crawler rules are grouped by provider, and fetch, indexability, and extraction details sit in a collapsible evidence section. The layout uses the full screen on mobile and records exactly when the page was checked. Repeated checks of the same URL can use a result stored for up to 30 days, making shared and revisited reports available immediately. A "Run a fresh check" action requests the live page again under the same verification and usage limits. The extraction measure now compares visible text inside the main content instead of comparing text with raw HTML bytes. That avoids penalizing framework-heavy pages simply because their markup is large. Internal-link evidence also focuses on links within the main content and quotes readable anchor text rather than markup fragments.
The robots.txt checker puts crawler decisions in one report
Results now open in a dedicated report instead of below the form. The report begins with the number of search, training, and user-fetch crawlers allowed for the checked path, then shows the winning directive and source line for each supported bot, grouped by provider. It remains readable on a phone without horizontal scrolling. Successful checks are cached for up to 30 days. Definitive errors are kept only briefly, and network failures are not cached. The report shows when the file was fetched and whether the result came from the cache. After a robots.txt change, "Re-check now" bypasses the stored result and reads the live file.
The AI Traffic Checker separates local analysis from URL checks
Running an analysis now opens a full-screen report with AI sessions, sources, recognized rows, and broken destinations at the top. Sections for sources, landing pages, URL status, and data quality follow in one scroll. The drop zone maps common GA4, Plausible, and Matomo columns and asks for help when a required column is missing. CSV rows are analyzed in the browser and are not uploaded. Only the deduplicated URLs selected for status checking are sent to the protected checker. Status results are cached for 30 days and show their age. A manual re-check bypasses the stored result and counts against the existing daily limit. Browser verification and a silent trap field reject automated submissions before they reach the checker.
Brand Voice Analyzer can profile a public page by URL
URL mode now fetches a public page, extracts its main text, and analyzes that text in the browser. When the page can be fetched, sentence rhythm, perspective, style markers, recurring phrases, and writing guidelines open in a focused full-screen report. Successful fetches are cached for 30 days, and the report shows the timestamp and cache state. Definitive fetch errors are cached for five minutes; transient failures are tried again on the next check. The extracted sample is capped at 100,000 characters, and URL checks are protected by browser verification. Paste mode makes no server request: its sample goes directly to local analysis in the browser.
Featured Snippet Checker can now inspect a live page by URL
The free Featured Snippet Checker can now fetch a public page directly. Paste a URL and the report extracts the main content, reviews answer structure and heading hierarchy, and shows whether important passages can stand on their own. The result opens in a focused full-screen view instead of a narrow column beneath the form. Checked pages can be reused from a snapshot stored for up to 30 days. The report shows when that snapshot was taken, so an instant repeat result is never confused with a new fetch. A short browser verification protects the public URL check from automated abuse. Pasted-text analysis remains local in the browser.
Contextter's free checks are easier to find where they help
The six free checks now appear next to the work they support. Site Audit points to AI Crawler Checker, Keyword Discovery to the People Also Ask Tool, SEO Monitoring to AI Traffic Checker, and the technical SEO solution page to the robots.txt checker. The homepage introduces the free-tool family, and the platform page links to the complete overview. Each recommendation says which question the tool answers and makes clear that no account is required. People can move from a product concept to a bounded public check without first searching the site for the right utility.
AI Crawler Checker shows what AI crawlers can actually access
The free AI Crawler Checker now examines one public URL and shows what a crawler can actually reach. It follows valid public redirects, checks the final site's robots.txt, and reports page access, indexability, canonical and snippet controls, crawler-specific rules, extractable content, heading structure, and internal-link context. Every verdict comes with the evidence behind it. The report includes redirect steps and relevant X-Robots-Tag directives instead of reducing a complicated setup to a vague yes or no. Compressed responses are handled within the same fixed check limits, while unsafe or private destinations remain out of scope. The checker does not execute page JavaScript or send the inspected content to an external text model. That boundary is visible in the report, so teams can understand both what was checked and what still needs a browser or manual review.
AI Traffic Checker now verifies referral URLs
The free AI Traffic Checker can now verify a bounded list of public referral URLs. For every address, it reports whether the page responds, where redirects end, which final URL was reached, and why a check failed. Each URL is checked independently. If one source is unavailable, the other results remain usable and the failed check stays visible instead of being folded into a misleading success state. Public-address validation, fixed response limits, traffic controls, and timeouts keep the free check predictable without hiding partial results.
AI robots.txt Checker explains crawler access rule by rule
The free AI robots.txt Checker now reads one public site's robots.txt and explains how its declared rules affect known AI crawler agents. It distinguishes allowed, blocked, and conflicting cases instead of turning the entire file into one unsupported verdict. For each crawler, the result shows the matching directive and its source line. That makes broad user-agent rules, more specific overrides, and contradictions easier to review. The check accepts only public destinations and uses fixed content, time, and request limits so a malformed or unusually large file cannot turn a quick diagnostic into an open-ended operation.
Brand Voice Analyzer now builds a complete private style profile
The free Brand Voice Analyzer now turns a 100-word-or-longer writing sample into transparent sentence, paragraph, punctuation, perspective, marker, repetition, and lexical-variety evidence in English, German, French, or Spanish. Samples from 300 words receive the full profile; shorter accepted samples are clearly marked as limited. The complete analysis stays in the browser, so even a sample near the 100,000-character limit does not tie up the interface. Submitted text is never uploaded, logged, or sent to an external text model. The resulting brief can be copied, and the structured profile can be downloaded as JSON without including the original sample.
Featured Snippet Checker handles large and ambiguous documents more clearly
The browser-based Featured Snippet Checker now skips empty structures when it looks for a direct answer. It reports the length of the selected passage and points out dependencies that make an answer difficult to understand without surrounding context. Large documents now enter a visible analysis state before local processing begins. Findings, evidence, outlines, detected structures, and question sections appear as separate previews. The on-page result remains bounded even when a document repeats thousands of headings, while Markdown, checklist, and JSON exports retain the complete set of findings.
People Also Ask Tool separates observed suggestions from assumptions
The free People Also Ask Tool now collects a bounded set of observed Google Autocomplete suggestions for one topic, language, and market. It groups the returned ideas into questions, comparisons, alternatives or reviews, and utility searches, and shows which source strategy produced each suggestion. The report distinguishes a live observation from a previously stored result. It does not present autocomplete suggestions as a copied People Also Ask box, search volume, ranking evidence, or frequency data. Clear empty and partial states show when the source returned less than expected, while CSV and JSON exports preserve what was actually observed. A full reset makes repeated research runs easier to compare.
Six free SEO tools first opened with honest preview pages
On July 30, the free tools hub opened six pages covering crawler access, question discovery, answer structure, writing voice, and AI referrals. At that release, each page explained the input, evidence, method, an illustrative report, and where the result could lead inside Contextter. Those first pages did not run an analysis. The previous SERP Analyzer form, which never produced a report, redirected to the hub instead. The preview state was temporary: later releases moved each tool to a live engine once processing, abuse protection, limits, and result validation were ready. The hub now marks all six tools as live.
Action Center saves calibration answers against the current profile
When a business-fit question comes from an older Action Center report, choosing "relevant" or "not relevant" now applies the answer to the current business profile. Existing calibration choices are kept, so a profile refresh no longer turns the next answer into a revision conflict. The buttons wait until the current profile is available and lock while a choice is being saved. This rebasing applies only to calibration answers. A direct edit to an outdated profile is still rejected rather than overwriting newer work.
Product limits now use one server-side policy catalog
Dashboard, Action Center, Domain Overview, Keyword Research, Competitive Research, Position Tracking, Site Audit, Activity, and the Keyword Database now use stable definitions from one policy catalog for the boundaries connected to it. Product, plan, and safety limits remain separate, and each eligible request resolves one coherent policy snapshot. A lower connected limit applies to the next eligible request; guidance shown in the interface is not the final authority. Limit checks happen before paid work starts. If a request exceeds its current allowance, Contextter keeps the input available, starts no paid run, and reserves no balance. Not every definition is editable: deployment-only and diagnostic values stay fixed, while definitions that do not yet control a verified product boundary remain read-only.
Support replies stay in the original email conversation
Each bug report or help request now has a ticket reference linked to one email conversation. When the Contextter team replies, the message uses the existing conversation and standard email reply headers, so separate messages do not have to be matched by hand. A customer reply is attached only when its conversation or ticket reference and sender can be verified. A verified reply reopens a resolved ticket and returns it to Needs reply; duplicates are ignored. The team must reopen a resolved ticket before sending another response.
Competitor metrics refresh after stored SERP runs
Shared keywords, covered volume, average position, and keyword gap used to change only when someone selected "Recompute" in the competitor view. They now refresh automatically after a tracking or Keyword Database SERP run stores new results. The calculation uses the workspace's stored data, so it does not make another paid request or reserve balance. A newly catalogued domain still needs to appear in stored SERP results before those figures exist. Until a stored run records it, the four metric cells show a dash and explain why no value is available. A numerical zero now represents a measured result rather than missing data.
Deep research now has a larger result budget than Quick
On July 27, a Deep run could return fewer usable keywords than a Quick run from the same seeds. Its expansion was narrower, and some suggestions arrived without the metrics required for import. This release widened the Deep pass, added bounded follow-up expansion, and checked the strongest candidates for metrics. The recipe has been refined since then. Deep currently has a larger source and result budget than Quick, with a cap of 2,000 deduplicated rows compared with 600. These are ceilings, not promised yields. Coverage depends on the available data, and a row without metrics remains visible but cannot be imported. The estimate shown before the start includes the paid steps selected for the run.
Keyword research match modes now show their results
Switching a research run to Phrase, Broad, Exact, Related, or Questions used to filter only the rows that happened to be in the first result window. A valid match farther down the run stayed invisible until someone clicked "load more" several times, which made a populated run look empty. Match modes now look farther into the run, so selective matches can appear on the first page while large runs keep a bounded search window. The workbench also requests the next batch while a filtered result is still incomplete. The filter bar shows how many candidates match the active mode, and the empty state distinguishes between three different situations: the search is still running, no match has been found yet, or the available candidates have all been checked.
Position Tracking shows live measurements and recovers stalled runs
A measurement in progress no longer looks like a failed one. The run log, run-health chart, and a live band on the Position Tracking page update as results arrive, for example "2 of 4 loaded." Missing results are counted only after the run has reached a terminal state. Until then, the interface reports coverage rather than drawing a completed red bar from unfinished work. Pressing "run now" while a healthy run is active does not replace it. If the click starts nothing, the response names the reason: another measurement is running, the tracker is not active, EUR Balance is insufficient, or the monthly budget cap has been reached. The interface no longer confirms a start when no run was created. SERP trackers also expose a separate fast action. It sends that single manual measurement through the priority queue and shows its estimated EUR cost before the click. Scheduled measurements keep their standard queue and price. A tracker configured for desktop and mobile dispatches both device runs as one group, and the progress band reports their combined coverage instead of showing two unrelated half-runs. If processing stops reporting after result requests have already been paid for, the run is no longer abandoned indefinitely. Recovery reuses the registered requests, collects any results that became available, and writes them through the same per-keyword settlement path as the original run. Results are not ordered or charged a second time. A fully recovered run succeeds; incomplete evidence stays partial, and an unrecoverable run ends as failed with a stated reason instead of remaining active forever.
Internal linking gets an actionable score
The old internal-linking card led with an average percentile that was structurally 50 and two correlation coefficients. Those figures described the calculation, but they did not tell you whether the site's link structure needed work. The card now reports one score from 0 to 100 and one of four verdicts: Strong, Solid, Improvable, or Weak. A short state sentence explains the result and the next sentence names the weakest part to address. Three scored aspects show how the verdict was formed: whether important pages are reachable at a sensible depth, whether internal authority is distributed without becoming flat or overly concentrated, and whether internal-link density follows the hierarchy. The raw correlations and concentration share remain in the method tooltip for readers who need to inspect the calculation.
Legal pages match the website and fill content gaps
Privacy, Terms, Cookies, and Imprint now use the same navigation, branding, and footer as the rest of the public website. The reading layout adds clear section boundaries, restrained line lengths, and tables that remain usable on a phone. A document switcher links the four pages without sending readers back through the footer, and it keeps the selected language. The imprint now names the current operator with a postal address, VAT ID, and contact address. It also distinguishes that operator from Contextter UG (haftungsbeschränkt) i. G., which is still being incorporated, and replaces the outdated media-law reference that appeared before this update. Several gaps in the legal copy were closed at the same time. The Terms explain EUR Balance from plans, top-ups, and trial balance instead of rendering empty list items. The Privacy Policy identifies the controller, gives the stated legal basis for each processing category, and explains the right to complain to a supervisory authority. The Cookie Policy separates the signed-in application's cookies and product analytics from the public website and help center, whose standard measurement setup does not use analytics cookies. German, French, and Spanish versions carry the same sections rather than falling back to incomplete English fragments.
Pricing copy in every language and prerendered marketing pages
Plan names, descriptions, feature lists, and calls to action on the pricing page now use the selected German, French, or Spanish catalog instead of silently falling back to English. Prices and plan limits still come from the shared plan configuration, so localization changes the explanation rather than creating a second pricing source of truth. Most marketing routes are prerendered again. They no longer wait for request-time data they do not use, which removes unnecessary server work from each visit. Blog and glossary routes remain dynamic where preview and filtering require fresh data.
Site Audit explains what it keeps and how crawl quotas count
Site Audit crawl history now has an explicit lifecycle. Recent runs and at least the ten newest terminal runs keep page-level evidence for comparisons and fix verification. Before an older run is compacted, its expiry is announced. Compaction removes heavy page detail but keeps the summary and the evidence used for health history and trend charts. Active comparisons or exports postpone that cleanup. After roughly six months, one completed run per calendar month remains as a compact long-term anchor; if a month has no completed run, its latest partial run can fill that role. Other runs in the same period can be removed. Runs past twelve months are removed except for the site's newest terminal result. Up to five runs per site can be pinned against earlier compaction, but a pin does not override the twelve-month boundary. An archived site has a seven-day recovery window before its audit history is deleted. Crawl quotas are separate from URL limits. The current standard plan values are fifteen full crawls and ten probe runs per organization and calendar month; the effective values can differ when plan or administrative limits are changed. The start dialog shows the applicable allowance, remaining runs, and reset date. Each crawl still uses the URL ceiling of its plan. Active and completed full crawls consume a quota slot. A cancelled, failed, or partial run with fewer than ten completed pages does not, and a run skipped for insufficient EUR Balance never started and is not counted. This keeps a failed start from using the same allowance as a crawl that actually processed the site.
Breadcrumbs show where each public page belongs
Public product, solution, tool, legal, blog, and glossary pages now show where they sit in the site. The breadcrumb leads from the home page through the relevant section to the current page, and every intermediate level is a working link. Related topics keep their product context: keyword research and tracking sit under the Keyword Database, while technical reports sit under Site Audit. The same hierarchy is included as BreadcrumbList structured data. Search engines can use it to understand the page relationship and may show that path in a result, but the presentation in search remains their decision.
One contact address across the public website
Public contact links now point to info@contextter.com. That includes the company and legal pages, privacy information, structured company data, contact forms, cancellation and withdrawal fallbacks, and newsletter error messages. All of these surfaces now use the same address.
Domain Overview puts ranking movement in context
Domain Overview now shows ranking distribution as a stacked history. The chart follows the same domain through the Top 3, positions 4 to 10, 11 to 20, 21 to 50, and 51 to 100; its upper edge is the total number of ranked keywords. That makes a growing total distinguishable from a real move into stronger positions. Search intent is calculated across the persisted ranked-keyword set, not only the rows currently loaded in the table. Each intent shows its share, keyword count, and estimated traffic. Competitors appear on a logarithmic positioning map with ranked keywords on one axis, estimated traffic on the other, and shared keywords controlling bubble size. Source context stays quiet unless a section genuinely uses a different data state from the current profile.
Action Center groups internal-link suggestions by target page
Internal-link recommendations became one entry per target page. Previously, each stored link suggestion created another row, allowing the same page to appear several times in the recommended order. The grouped entry collected the suggestions for that target. The figure beside the entry became the count of bundled link suggestions. It no longer displayed an internal quality score under a label such as “69 concrete link recommendations”. Recommendations also replaced storage-oriented wording with a decision the user could verify. A recorded position 9, for example, became a prompt to review the ranking page, search result, intent, and available on-page evidence before choosing an optimization. It was no longer presented as proof that the page would climb. The page title also appeared only once.
Workspace Home adds a visual ranking summary
The **Your rankings** card began drawing the average position of tracked keywords over time and split the latest recorded positions into Top 3, Top 10, Top 20, and Top 100 bands. The chart direction made improvement and decline visible without changing the underlying position values. A short footer stated what was measured, how often the schedule ran, and when it last completed. The card replaced two text-only panels. The keyword trend chart also named its subject, **Visibility of your domain**. Its Keywords, Traffic, and Top 10 series described the domain-level organic evidence rather than the selected list or the separately tracked keyword set. The activity feed moved out of the main area but remained one click away in a compact card. The full log stayed on Activity, and the dashboard help tour followed the revised layout.
Domain Overview adds controls for loaded evidence
Domain Overview began allowing the loaded competitors, ranking keywords, top pages, anchors, referring domains, and linked pages to be searched and sorted without starting another paid analysis. Position groups filtered the keyword evidence directly, while competitor rows and the traffic comparison highlighted the same selected domain. The growth charts shared a 6, 12, 24, or 60-month window. Active controls stayed in the page URL, allowing a focused view to survive a refresh or be shared. Every result counter stated that it referred to loaded evidence, keeping a partial snapshot or paginated result identifiable.
Keyword Research closes runs with expired balance reservations
Keyword Research began closing a run with an expired EUR Balance reservation through the same visible failure path as a processing or handoff failure. The unused reservation was released, the run received a support code and activity record, and another research request could start without stale capacity from the earlier run. Timeouts, inactive reservations, stalled processing, cancellations, and authorized recovery retained distinct diagnostic codes instead of collapsing into a generic internal error. Customers saw the stable explanation and support code; operational detail remained available only to authorized operators.
Site Audit publishes retained link evidence with visible progress
Site Audit began evaluating contextual internal links and repeated anchor text from the retained link graph rather than a fixed first-page sample. Large crawls therefore kept findings beyond the first 1,000 matching links whenever the retained graph was complete for that rule. The processing indicator reserved a measured final-publication stage and named the work in progress, such as link metrics, issue summaries, aggregates, or the Health Score. It did not move to 99% before that report work had begun. Audits also identified identical title and H1 text, external nofollow links, and unnamed external links as review diagnostics. Valid decorative images, accessible image links, intentional resource links, and an absent `llms.txt` remained outside the defect count. Empty image alternatives became visible without being confused with a missing attribute. The audit distinguished likely content images from explicitly decorative markup and kept both outside the Health Score until review. Issue exports showed known categories, evidence sources, and target URLs for duplicate anchors instead of generic labels. Repeated template patterns used a concise, representative URL sample.
Site Audit validates structured data and reports measured performance
Site Audit began validating JSON-LD, Microdata, and RDFa beyond syntax. It checks Schema.org types and properties, basic value formats, deprecated vocabulary, and, for supported Google result types, the difference between required and recommended fields. The overview separates clean, review, blocked, and unmarked URLs, groups repeated template problems by cause, and keeps the item-level evidence behind every verdict. History and URL filters make it possible to follow a type or result feature across crawls without treating a sample as full coverage. Performance reporting now keeps crawl response time, lab measurements, and available field data separate. Every run states how many eligible URLs were planned, measured, or failed. Missing CrUX data stays unavailable, and a slow Lighthouse measurement can reduce performance coverage without failing the completed crawl. Measurement profiles are versioned, interrupted work can continue, and partial coverage remains explicit in exports and comparisons.
Action Center shows one recommendation at a time
The Action Center was redesigned around one practical question: what should you review next? Instead of opening with a dense multi-column dashboard, it showed one recommendation with a plain title, the reason for its current position, and the three headline measures behind it. From that card, the recommendation could be started, saved for later, or marked as not relevant. The last choice became an explicit business-fit signal rather than silently changing the shared guide. Step-by-step guidance, the supporting evidence, ranking feasibility, and optional data enrichment stayed available in the detail view. A grouped list kept the broader guide in **Now**, **Up next**, and **Watch** bands, with in-progress items still reachable. After the user had reviewed the current set, “done for today” described the state of that review queue, not the health or completeness of the website.
Competitive Research keeps paid comparisons recoverable
Competitive Research began reusing the same comparison when a browser or network retry repeated the request. The balance reservation stayed attached to that operation, allowing an interrupted handoff to recover without creating a second paid run. Full competitor analyses published one complete ranking generation at a time. If source retrieval, score calculation, or finalization failed, the previous successful data remained visible and unused reservations were released. A partly written result did not replace the last usable comparison. Comparison reports distinguished running, partial, failed, empty, limited, and available modules for each domain. Coverage, freshness, applicable limits, and support codes stayed visible. The report also added decision guidance, detail dossiers loaded on demand, stable shareable URLs, paginated history, and a CSV export that preserved missing data instead of turning it into zero. Quick comparisons marked which modules required a Deep analysis and offered a prefilled upgrade. If Quick and Deep started close together, they reused the same running overview data instead of reserving and requesting it twice. Deep comparisons consolidated already purchased keyword-gap evidence across the selected competitors. The bounded overview prioritized gaps shared by the most domains, kept unavailable metrics visibly unknown, disclosed sampling, and handed individual or grouped opportunities into Keyword Research without a new source request.
Workspace Home shows measured values instead of setup prompts
The average-position and opportunity figures on Workspace Home began using the workspace's recorded evidence. Average position read the active rank tracker, including a tracker with hand-picked keywords. The opportunity count used the same workspace-wide evaluation as the Action Center. A measured zero appeared as zero rather than as a prompt to configure work that was already running. Every point in the keyword trend received a larger hover target. Its tooltip stayed inside the visible card, and a legend named both lines when the Top 10 view also drew the Top 3 series. The chart stopped creating a separate small scroll area inside the card. The tracking panel added a compact trend for the primary schedule's average position beside its keyword count. Once every setup step was complete, the checklist collapsed to one confirmation line. The competitor card explained that a blank marker meant "not measured yet" rather than a broken result. At this release, new workspaces also saw what their available starting balance covered and where they could add funds.
Domain analyses separate missing data from an empty result
Domain analyses began stating the direction of every keyword gap: the first domain ranked while the comparison domain did not. When the user analyzed a competitor, the workspace's tracked domain became the default comparison. Analysis of the workspace's own domain offered its tracked competitors and selected the only one automatically when there was no real choice to make. Each data section kept its own retrieval state and coverage. A failed source request appeared as missing evidence rather than as a genuine zero-result finding. Limited samples showed how many rows were loaded against the reported total. Analysis time remained separate from source freshness when a freshness timestamp existed. Starting another analysis from a saved snapshot preserved its market, language, keyword scope, and comparison domain. Already purchased fields were retained more completely, including shared and full competitor metrics, page-level organic metrics, keyword-gap landing pages and traffic, backlink spam and crawl facts, and indexed-page totals. The history marked complete, partial, running, and failed attempts directly. It opened the latest usable result instead of allowing a newer failed attempt to hide it, and showed a loading state while older keyword, competitor, page, and link rows were being restored.
Report a problem from the page where it happened
Signed-in users could report a bug or ask for help from the shared header on Contextter's main workspace pages. The draft included the current account, workspace, page, and active report area, leaving the user to describe what had happened. The description remained in place if sending failed. Closing a report with unsent text required confirmation, and a successful submission created one report for follow-up. When an error view showed a support code, it offered the same report action and added that code to the draft. The user could describe the interrupted task without copying diagnostic text by hand.
Keyword Research makes interrupted runs recoverable
Keyword Research began distinguishing handoff, waiting, active processing, and finalization instead of showing one indefinite running state. A run that was not accepted in time or stopped responding closed and released its unused balance reservation. An active run could also be cancelled directly. Repeated browser or network requests reused the same research operation instead of creating another reservation. Large imports split into several parts kept one target list and resumed after the last confirmed part. Filtered result pages looked ahead within a strict bound, so later matches did not remain hidden behind an empty page. Customer-facing errors used stable, localized explanations and a support code instead of exposing source or execution details. Authorized operators retained the diagnostics needed for follow-up. Results reused existing keyword and search-result evidence when it was available: cached SERP features and top results, search trends, related parent topics, a clearly labelled traffic estimate, and domain-relative difficulty. Sorting and paginated history remained usable on larger result sets. Missing or partial evidence stayed visibly unknown. Saved research data could be exported as a filtered and sorted CSV. Each result showed its source and, where available, the seed that produced it. A previous run could prefill another request from history. The current price remained visible, and the new request did not start before confirmation.
Domain profiles retain the latest usable evidence
Domain Overview began using a persistent profile. A new analysis extended the existing evidence, while a temporary source failure did not displace an older successful state. Each source state remained traceable as a dated snapshot. A discovered competitor could be carried directly into a new keyword-gap analysis. The competitor and the workspace's own domain were prefilled in their correct roles. The price preview and explicit confirmation still came before the paid request.
Position Tracking keeps market and device contexts separate
Position Tracking began keeping desktop, mobile, country, and language measurements separate in saved results, history, comparisons, and exports. Tracking setup allowed the market and language to be selected instead of using a fixed default without showing it. Report navigation stayed stable while the user switched between reports and tracking jobs. The Cannibalization report remained available from Jobs, and its empty state explained when the recorded search results contained no simultaneous conflict between the site's URLs. The Rankings report added tags plus quick filters for Top 3, winners, losers, and keywords that were not ranking. Filters ran before server pagination, remained in the page URL, and fed the same CSV export. Values that spreadsheet software could interpret as formulas were neutralized in the export. The Positions chart separated improvements, declines, new rankings, losses, and unchanged keywords. Pages showed which landing pages contributed the most estimated traffic. Jobs exposed run coverage and missing data over time. SERP Features distinguished appearances owned by the workspace, owned by a competitor, or lacking reliable attribution. SERP-feature ownership distinguished “not owned” from a result without reliable attribution. Several own URLs counted as cannibalization only when they appeared in the same measured search result. A URL switch between days and older history without concurrency evidence remained a separate change. A multi-device run settled as one group. Impossible progress values were rejected, and stale-run recovery closed abandoned work and released unused reservations. Required search-result updates and ranking history were stored together, preventing a success state when part of that history was missing.
Site Audit applies the 5,000-page limit consistently
Site Audit began applying the 5,000-page limit consistently when a domain, crawl, or recurring audit is configured. Older saved settings with a higher value were reduced for future crawls without changing historical crawl or billing records. Large results also reported their preparation state more precisely. A result did not appear complete while a required summary still lacked eligible pages. Page details loaded evidence for the active section, kept an older crawl selected when opened through a direct link, and explained when that crawl's detailed evidence had expired while its summary remained. URL details stayed inside the same Site Audit navigation and content frame as Pages, with the selected URL in the breadcrumb instead of a second page header. The current product limit remains authoritative for future crawls.
Site Audit comparisons use clear crawl names and matching units
Each Site Audit crawl received a name containing its full date, time, year, and chronological run number for that day. Several crawls from the same day could therefore be selected without relying on their URL or issue counts, and crawls from different years remained distinguishable. Compare kept the earlier and later crawl in chronological order, loaded the available issue groups, and reset the pair when the selected domain changed. Totals distinguished issue occurrences from affected URL instances, so an increase and a decrease used the same unit. Opening a comparison row switched to a crawl in which that issue was present. Compare could load older crawl pages directly, including runs outside the newest 20 entries. It also waited for a run's published results and kept severity changes assigned to the correct category in each crawl.
Site Audit distinguishes a delayed start from a failed crawl
Site Audit began distinguishing a delayed processing start from a failed crawl. An accepted crawl remained queued, retried automatically, and offered a manual retry without creating or charging for a second run. If processing remained delayed, the notice could open a prefilled problem report with the support code and crawl context already attached.
Site Audit separates confirmed defects from review signals
Site Audit began separating confirmed defects from signals that still need review. Corrupted titles and descriptions can be reported as defects, while character length, sparse copy, static render-blocking candidates, and simple cache-policy checks remain advisory unless stronger evidence exists. Intentional forms, galleries, downloads, lightboxes, and decorative `alt=""` markup are not penalized solely for being short or image-led. Repeated anchor and resource patterns are grouped by their shared cause, and samples are labelled as samples. External destinations receive a browser-like confirmation before they are called broken; authentication or challenge pages are not suggested as replacements. Contextual-link advice stays limited to content pages and appears only when the relevant link evidence is complete. Progress reaches 100 percent only after findings, link analysis, Health scoring, and report evidence have been published.
Site Audit keeps issue evidence tied to the selected crawl
The Site Audit Issues tab began anchoring its catalog and history to the selected crawl. Categories, sources, affected-unit types, issue movement, and fixed issues came from published audit data rather than being inferred from the page currently loaded in the browser. Incomplete and failed crawls no longer appeared complete. Bounded counts were labelled as lower bounds, missing history remained visibly missing, and loading more affected URLs or assets retained its loading state instead of briefly showing an empty result. Issue reports kept copying implementation guidance separate from opening an agent-ready handoff. The report retained the full run-level evidence count when only part of the detail list was loaded and explained when more findings could still exist. A failure in one Issues panel stayed inside Site Audit and offered a retry for that section. Reconciliation also closed stale issues when a fresh crawl returned no matching finding, including older cases outside the previous processing window.
Site Audit explains internal link depth and opportunities
Site Audit began calculating click depth as the shortest internal-link path from the start page. Overview and Statistics showed the depth distribution, while Page Explorer could filter and sort URLs by click depth, reachability, incoming links, outgoing links, and internal authority. When two crawls had compatible exact-depth evidence, Overview also showed changes in median depth, P90 depth, and unreachable pages. The Health Score gauge kept a three-digit score legible inside its ring. Internal Links loaded a large site page by page rather than keeping the full URL inventory in the browser. Each URL showed a representative shortest path, named relationship and occurrence counts, and a relative-authority estimate with its basis visible. On desktop, Internal Links and Page Explorer stayed inside the available viewport while long URL and relationship lists scrolled in their own panels. For audits within the 5,000-page limit, internal-link opportunities evaluated the eligible URL set before publishing a bounded action list. Existing links, unsafe targets, incomplete graph evidence, and weak topical matches stayed out. Each action carried separate evidence for target need, topical fit, source authority, placement feasibility, and risk. Ranked actions remained in the Action Center so review and completion used one shared state.
Statistics publish after crawling while page details keep context
Crawl statistics began publishing when crawling finished instead of waiting for later external-link and asset checks. Statistics could therefore show response health, click depth, indexability, and discovery sources while those follow-up checks continued. Opening a page from Pages retained the crawl context. If a copied or shared link did not include a crawl, Contextter resolved it to the latest crawl in which the page had been recorded instead of rejecting the page until a crawl was selected by hand. The page detail view kept the Site Audit frame. Domain and crawl selectors remained available, and changing the crawl loaded the same page in that crawl. The other Site Audit tabs stayed reachable without using a back link first. Page details stored the selected tab, link direction, filters, asset section, and issue severity in the URL. Previous and next moved through the loaded Pages result without loading a whole crawl into the browser. Inspecting a linked page offered a direct return to its source. Link and issue filters ran before pagination, allowing matches beyond the first loaded batch to appear. A missing page or crawl showed a recoverable explanation instead of a generic failure.
Action Center recommendations now account for confirmed business fit
Action Center began using confirmed business context alongside keyword, ranking, competitor, domain, Search Console, Site Audit, and internal-link evidence. Topics outside the offering were held back, while uncertain matches became questions instead of confident instructions. Difficulty, intent, page readiness, movement, and the site's recorded strength shaped keyword recommendations; missing evidence stayed visible as a data need. The five decision goals now produce different portfolios rather than the same queue in a different order. Recommendations link to their exact working context, can be saved with an editable priority, and include a free deterministic plan with execution and verification steps. If one missing paid data point could change several decisions, Contextter groups the affected keywords into one proposal and shows scope and price before confirmation. Optional AI suggestions remain separate from confirmed business facts until the user accepts them.
Site Audit waits for crawl evidence before publishing a report
Site Audit began waiting for queued page analysis before marking a crawl complete. The crawl overview, issue groups, URL totals, and Health Score were published from the same completed evidence state rather than from an earlier intermediate result. If final publication was interrupted, Contextter resumed that step without crawling the website again. Recovery was paced, and temporary write-limit failures received bounded retries. An interrupted publication therefore stayed separate from the completed crawl evidence instead of starting several report rebuilds or rewriting the crawl itself as failed.
Home opens the Position Tracking workspace reliably
Opening Position Tracking from Workspace Home now reached the tracking workspace even when Contextter still had to prepare part of the view. The setup link stopped at a visible loading state instead of falling into an error screen before the tracking controls appeared. Current access still depends on the workspace's enabled features and permissions.
Site Audit findings now separate evidence from repeated symptoms
Site Audit began recognizing valid alt text, responsive images, accessible link labels, navigation, resource hints, and downloads more precisely. Repeated resource problems are grouped by the affected asset instead of being multiplied across every source page, while the report keeps occurrence counts separate from unique URLs and assets. Overlapping symptoms can share a likely cause without being presented as proven causality. External links now receive browser-compatible confirmation before they are called broken. Login walls and unstable access blocks remain unverifiable, and redirect checks preserve meaningful trailing slashes. Contextual-link findings appear only when the crawl has complete body-link evidence; otherwise the report states that the evidence is partial. A crawl also stays in processing until its findings and Health Score are published, so exports and implementation guidance cannot present an unfinished projection as a completed audit.
Site Audit separates website health from crawl confidence
Site Audit began calculating Health from the pages and checks that were eligible in a particular crawl. Many low-impact findings no longer forced the score onto an artificial floor. Failed or incomplete crawl work appeared in the confidence state instead of being mixed into website health. Every published score was labelled Measured or Provisional. When the available evidence could not support a score, Contextter showed what was missing instead of filling the gap with a number. The overview also named verified blocker caps, the weakest score categories, and the main drivers as unique affected pages against the real eligible-page denominator. Drivers were not presented as additive point deductions because several rules can overlap on one page. The Sites overview, crawl history, comparisons, portfolio summaries, and Health drop alerts used the same persisted score snapshot. Older summary-only crawls remained visibly unsupported. Incompatible runs produced no Health delta, and alerts compared only measured crawls with matching scoring version and crawl scope.
Site Audit separates live crawl speed from processing time
Running Site Audits began showing their average pages per minute directly below Crawl Time. The rate stopped changing when crawling finished, so later report processing did not make the completed crawl appear slower. Processing Time began with the first processing work, even while crawling was still active. Crawl Time, Processing Time, and Total Time therefore described overlapping phases rather than suggesting that all processing waited for the last fetched page.
Action Center connects evidence across SEO workflows
Action Center began bringing evidence from keyword work, domain analysis, competitors, tracking, connected Search Console coverage, Site Audit, and internal links into one decision guide. Each recommendation showed its source, known limits, prerequisite, responsible product area, and a way to check the result. Business fit and ranking feasibility could hold back an attractive keyword instead of turning demand alone into a task. A workspace with little history received a conservative setup sequence, while a workspace with no qualifying action received an honest empty state rather than filler. Users could save recommendations to **My actions**, change their priority and status, and keep that list across later refreshes. Optional deeper data or an AI plan started only after confirmation. The AI plan worked on one selected action, used a reduced SEO evidence packet, excluded private documents and credentials, and could not silently replace the deterministic guide after a failed or invalid response. Historical plans remained visible while a refresh ran or failed.
Dashboard and Activity now explain every signal in context
Help on Home began following the workspace briefing from identity and data state through keywords, competitors, technical health, priorities, recent activity, product readiness, and learning resources. Each step named the source of the summary and linked to the detailed documentation for the workflow that owned it. Activity explained its bounded 28-day summary, newest-first event history, counters, status meanings, notification filters, support evidence, and access to older history batches. The guide also stated the ownership boundary: Activity recorded outcomes, while live controls and detailed state remained in the product area that created the operation.
Contextter turns SEO data into a guided next step
This release connected Domain Overview, competitors, Action Center, Keyword Research, the Keyword Database, and the historical Position Tracking surface into one guided workflow. Workspace Home showed which evidence existed, what was ready for review, and, where tracking was configured, when the next scheduled ranking check was planned. A step counted as complete only when the corresponding result existed in the workspace. Domain and competitor views opened with a concise situation report: what the current data indicated, why it might matter, which evidence supported the statement, and where to continue. Position Tracking separated movements marked for immediate review from later checks and watch items. Missing search volume did not create an artificial urgency signal. Keyword Research added selection recipes for ideas labeled reachable, commercial, or supported by competitor evidence. When previously purchased top-10 results existed for the same market, language, and device context, the workspace could group keywords by observed SERP overlap without another data purchase. Site Audit grouped findings by likely remedy area and labeled that group as a planning aid rather than a proven shared cause. Action Center kept the immediate queue focused while the broader list grew or shrank with qualifying evidence. Each admitted action stated its intended benefit, estimated effort, evidence, prerequisites, and next step. The workflow described here is dated; current navigation and tracking availability remain authoritative in the product.
Workspace Home expands its evidence briefing
This release expanded Workspace Home beyond Site Audit and the Keyword Database. The page was organized as a briefing on the domain, possible next actions, recent outcomes, and the evidence held by each product area. The workspace domain led the page. Its summary band showed observed organic keywords, top-10 rankings and their change since the previous analysis, estimated traffic value, open Site Audit findings, and keyword-inventory size. Each number linked to the product area that owned its evidence. Below it, one column drew possible work from the existing priority list. A second, **What happened**, listed completed crawls, domain analyses, keyword-research runs, and data refreshes across products, with a link back to each source. Site Audit and the Keyword Database retained their larger widgets, including list selection and finding trends. Compact cards represented Domain Overview, Keyword Research, Tracking, and Competitors. A product area with data showed its headline value and last update. An area without setup explained what evidence it could provide and offered one starting route instead of displaying zero as if it were a measurement. Areas unavailable to the current role were omitted. The final row linked to documentation and the latest Blog and Glossary entries available at the time of the page request. The layout used the available width on large screens and stacked the same zones on smaller screens. Brain, Research, and Content cards were removed from Home while those areas were still being developed, although their historical pages remained in navigation at this date. This entry does not describe the current Workspace Home or current feature availability.
Research help now follows each decision step
The Help walkthroughs in Keyword Research and Competitive Research began following the workbench from top to bottom instead of ending after a short introduction. They covered research modes, seed terms and domains, market context, live estimates, run evidence, filters, term groups, candidate selection, imports, saved runs, domain comparisons, history, market position, competitive signals, keyword gaps, coverage, list actions, and competitor details. Enter moved to the next visible step. Each step also linked to its localized Help Center topic when the reader needed the full explanation. In Domain Overview, the run selector stayed in the domain context row and remained readable in both light and dark themes. This entry records the guidance and page structure introduced in this release; the current workbench remains the source of truth for available modes and controls.
Keyword Research now starts from consistent local search signals
Keyword Research began generating suggestion ideas for the market selected in the research form rather than the location from which processing happened to run. The suggestions served as additional starting points and still passed through the same relevance, deduplication, and metrics checks before entering the result. Repeated Quick Research runs therefore used the intended market context without shrinking the candidate pool. The change improved consistency; it did not make separate live suggestion runs identical.
Workspace pages now share one clear page header
Home, Action Center, Domain, Research, Competitors, Tracking, Briefs, Site Audit, Activity, and Keywords adopted the same compact orientation bar. Page title, relevant workspace context, and primary page actions stayed in a predictable place. Controls that belonged to a particular view or dataset remained directly below it. In the Keyword Database, the main metrics shared a single-line context rail above the view controls, leaving more room for the keyword table without hiding the current data context. Header actions also followed one visual rule. Help used a blue information treatment, while ordinary page actions used the primary button color. Home kept the header focused on Help instead of duplicating Keyword Database and Site Audit navigation. Help opened a guided walkthrough for the current page and followed its visible areas in order. Domain Overview covered snapshot context, authority, rankings, competitors, keywords, links, and growth. The historical Tracking surface adapted the guide to Overview, Positions, Pages, SERP features, competitors, cannibalization, and schedules. Site Audit covered its ten workbench views, while a crawled URL adapted Help to Overview, findings, links, assets, schema, changes, or technical evidence. Each step linked to the matching localized documentation topic. Keywords kept its more detailed database onboarding behind the same entry point. This entry records the workspace navigation available at the time, including surfaces that are no longer part of the current core product.
Position Tracking stays responsive as your history grows
Position Tracking began isolating failures to the affected view. If one data source was temporarily unavailable, the tracker selector, other tabs, and schedule management remained usable. Only the affected area showed its support code and retry action. An unavailable optional Site Audit link also stopped without hiding the recorded ranking-page data. History loads were bounded to the selected context instead of sending every measurement to the browser. Trends showed the latest 30 points, competitor analysis loaded only while its view was open, the active competitor set was capped at 20, and schedule lists showed the latest 30 entries with a notice when older entries existed. Before a schedule could start, its cost estimate had to be current. Invalid keyword, language, location, device, or budget input was rejected consistently. List-based trackers supported up to 500 keywords per run at this release, while a larger list received a visible limit response instead of starting an operation that could not complete. The overview retained all four headline-metric positions when a value was unavailable and explained the missing data instead of substituting zero. The creation workbench was spacious but bounded, keeping domain, keyword selection, competitors, and schedule settings in view without covering the entire application. The Orders view used the available workspace width and kept one creation action in the page header. These tracking limits and surfaces describe the product at this date, not the current Contextter feature set.
Site Audit: one place for crawl history and one place to inspect a run
The History tab became **Crawls** and separated run history from inspection. Its table listed each stored crawl with crawled URL count, health, open findings, and the change in each value from the previous run. Selecting a crawl turned the same tab into a run inspector. The inspector summarized the recorded outcome in plain language. While a crawl was active, "Happening now" showed the current fetch stage and queue composition, and the inspector opened that section by default. The stored crawl log used pagination rather than a small sample. Users could page through its URL records, filter findings or redirects, and open a page's detail view. Error messages appeared below the URL as readable sentences rather than internal codes. Tables scrolled inside their own area and used the available height even when only one run existed. A URL detail page added a breadcrumb and back action consistent with the rest of the workspace. **Monitoring** was renamed **Automation** because schedules could start audits rather than only observe them. Each schedule showed its previous run and outcome and linked to that crawl. Schedules and alerts could be edited as well as paused or deleted, and each used its own creation form. **Crawl now** started an audit immediately. Schedule and alert cards retained their empty state after all records were deleted, so the tab still explained what could be configured.
Domain Overview is safer, richer and easier to reuse
Domain analyses gained a paginated history, visible storage limits, and a confirmed delete action. Repeating the same request after a network interruption reused its operation identity instead of creating another analysis or balance reservation. A paid request did not start when the number or value of active reservations could not be established within the release limits. Organic keyword rows added the observed ranking page, estimated keyword traffic, and competition when supplied by the source. The competitor panel retained its compact comparison and added a table with shared keywords, total observed organic keywords, average position, and estimated traffic. A selection dialog connected the snapshot to the rest of the workspace. Selected rows could be stored in a deduplicated `Domain · example.com` list in the Keyword Database while retaining available volume, difficulty, CPC, competition, intent, and language data. The same selection could seed Keyword Research, with the 100-seed limit shown before navigation. Across the paid Research, Tracking, Brief, Import, and Site Audit actions available at the time, Contextter stopped before an external data request when the active-reservation total could not be calculated exactly. The current product remains authoritative for today's paid actions, limits, and retention.
Site Audit: full site structure, link trends and cleaner statistics
The Site structure table began showing every folder recorded in the selected crawl instead of hiding smaller groups. It used the available screen height, scrolled independently, and kept column headers visible. The Internal Links overview added up to six per-crawl trends: internal links, average links per page, orphan pages, external links, `nofollow`, and links to redirects. Link Explorer and the link map also used the available viewport height. The run overview kept the same statistics and source values but separated them into flatter sections. Each finding's "Why this happens" section linked to a relevant glossary entry, including canonical tags, hreflang, and redirect chains. Domain and run pickers closed when focus moved elsewhere. Asset findings displayed the complete asset and source-page URLs and opened their evidence directly. The Issues overview reused the compact agent actions from an individual finding. **Agent prompt** opened a Markdown preview for the findings in the current filtered view. **Agent endpoint** created a scoped pull address only after explicit confirmation, without expanding a separate export workspace above the list. An optional guide explained the handoff to coding agents, from repository access through validation and a confirming crawl. The endpoint panel explained when a pull workflow was more useful than a copied prompt, how to pass the authenticated request to a coding agent, and why the temporary credential had to remain private. The credential was no longer placed in the URL, expired after one hour, and could be revoked from the same panel. Cancelled and failed crawls received a plain-language state and a possible next step, while internal error codes stayed out of the customer-facing view.
Site Audit monitoring makes schedules and delivery states visible
The Monitoring tab reduced initial setup to cadence and recipients. Weekly was the recommended default at this release, while advanced controls exposed timing, budget, URL limits, and triggers. Each recurring schedule showed its next planned run and could be paused, resumed, or deleted. If a run was skipped, for example because the prepaid balance was insufficient, the schedule card displayed the recorded reason. Notification cards sat beside the schedule, and an activity feed listed each triggered event with the known email-delivery state. The status distinguished recorded processing states; it did not treat acceptance by the email service as proof that the recipient had read the message. These scheduling defaults describe the release at this date.
Site Audit corrects statistics loading and click-depth scope
This release corrected two Statistics-tab behaviors. Statistics for a finished crawl became available without leaving the tab on "Statistics are being prepared" after processing had completed. Click depth was also limited to pages reached through recorded internal links from the start page. A page discovered only through the sitemap no longer increased the internally reachable group and appeared as "Not linked" for this measure. Existing crawl results kept their stored values; the corrected distribution began with the next crawl.
Keyword Research now explores topics more intelligently
Quick Research began expanding each topic through closely related searches and up to three related angles. It tested questions, prepositions, modifiers, comparisons, year and local intent, and A-Z variants, then sent a bounded candidate set to one shared metrics check. Deep Research extended that exploration through adaptive rounds. It followed relevant new angles, stopped when the additional yield weakened, and enriched a bounded set before returning up to 2,000 deduplicated keywords under the release limits. Starting keywords were counted while the user typed. The live estimate appeared in a fixed-width start button, preventing price refreshes from moving the controls or repeating the reserved amount elsewhere. Quick Research validated at most 360 suggestion candidates and returned at most 600 deduplicated keywords. At this release, the confirmed estimate was the charge ceiling, so a higher upstream cost was not added after completion. Before a paid data request, the run verified that it was still attached to the correct workspace and dataset. A failed handoff released its reservation. The activity view distinguished delivery, configuration, network, timeout, quota, and data-source failures instead of collapsing them into one message. These methods, limits, and price rules describe the product at this date; the current checkout remains authoritative.
Competitor Workbench: compare the right domains at the right depth
Competitor Workbench began turning domains observed in tracked search results into a maintained catalog. Users could add, remove, or pin relevant competitors while keeping the changing SERP landscape separate from the curated comparison set. At this release, up to 20 competitors could be active at once, and the larger candidate catalog remained paginated. A quick comparison covered the main authority, traffic, keyword, and link signals. Deep analysis added keyword gaps, intent, difficulty, top pages, and more detailed link evidence. Before either run, checkout itemized the estimate and reused recent snapshots or completed modules, so only missing data was requested. Results stayed as dated snapshots: changing the active set prepared a new comparison and price preview instead of rewriting an earlier result.
Internal Links rebuilt around traceable relationships
This release rebuilt the Internal Links area around the relationships and occurrences recorded by a Site Audit crawl. The **Overview** showed how many internal and external links the crawl found, how many pointed to redirects or carried `nofollow`, which crawled pages had no recorded incoming internal link, and which pages received the most internal links. Each count and row opened the corresponding filtered evidence rather than ending at a summary. In the **Explorer**, selecting a page opened its title, complete URL, navigation breadcrumb, and counts for incoming, outgoing, and external links. Full-width tabs separated incoming, outgoing, external, and backlink relationships, while placement filters distinguished content, navigation, footer, and other recorded regions. A **List / Map** switch changed the presentation of the same selection. **Page details** opened the complete page report and its findings without losing the selected link context. Repeated links between the same source and target appeared as one relationship. Its row retained the occurrence count, distinct anchor texts, and recorded page regions such as navigation, header, and footer, so deduplication did not remove the evidence. The **All links** table used its internal, external, broken, redirect, and `nofollow` summary tiles as filters. Any row could open the Explorer at its source page. All counts remained bounded by the selected crawl and any separately labeled backlink source.
Keyword Research moves from a form to a workbench
This release moved Keyword Research from a single form into a results workbench. A run could begin with keywords or competitor domains, a market, and a research depth. The checkout showed its estimate before confirmation, and the result opened as a filterable table with the available search volume, CPC, difficulty, and intent for each row. Match modes separated All, Broad, Phrase, Exact, Related, and Questions. A term rail showed frequent words in the current result set, while filters covered volume, difficulty, intent, source, and included or excluded terms. These controls worked on the data already returned by the run and did not start another paid request. A marker identified keywords already stored in the Keyword Database, and an "only new" filter hid them. Import remained explicit: users selected the rows to keep and chose an existing or new list. Recent searches stored each run with its market, keyword count, and settled cost under the retention rules available at the time. Reopening and filtering a stored result did not purchase the same data again. This entry records the July 2026 workflow; current retention, research methods, and prices remain authoritative in the product.
Position Tracking: competitor discovery, SERP-feature landscape, and a visual overview
The Competitors view began listing domains observed repeatedly in the top 10 for the tracked keyword set, including domains the user had not added manually. Each row showed shared keywords, best observed position, and average position. A domain could be added to or removed from the comparison. When retained search results covered earlier measurements, a newly selected competitor could use that stored history instead of starting with an empty series. The SERP-features view summarized which recorded results contained AI Overviews, featured snippets, local packs, image packs, and other features, how many tracked keywords were affected, and where the tracked domain was observed in that feature. Selecting a feature opened the corresponding keyword set. The overview gave visibility, estimated traffic, average position, and share of voice separate cards with trend charts. A stacked chart showed how the top 3, 10, 20, and 100 counts changed between runs. A fact line stated the tracked domain, device, language, market, keyword and competitor counts, search depth, and last update. Missing search volume remained unknown in estimated-traffic views instead of being rendered as zero. The Competitors view could compare visibility, estimated traffic, average position, top-10 count, or share of voice across the selected domains. The keyword table used pagination, and the overview trend could also plot how many tracked keywords had any recorded ranking. The creation wizard allowed the tracked domain to be changed in its first step. In the Positions view, each keyword had its own series and each completed measurement added a point. These tracking surfaces describe the product at this date and are not a promise about Contextter's current feature set.
Clearer paths to every public Contextter page
This release aligned public routes across the platform, features, solutions, learning resources, comparisons, and company information. Existing customer and comparison addresses stayed stable where possible, while retired routes redirected to the closest maintained destination rather than ending at a dead page. Navigation and page directories exposed the same route groups in each supported language. Public listings also tied their update signal to a meaningful source change, so an unchanged page did not receive a new date merely because the site was rebuilt. The release improved discovery; it did not certify that every linked page or translation was complete.
Site Audit: a real page for every URL
The Pages view began with internal URLs, while a visible scope control switched between Internal, External, and All. Selecting a page opened a dedicated URL route instead of an overlay. It showed the crawl-derived score, findings, HTTP status, response time, word count, and link counts, with separate tabs for findings, links and the recorded crawl path, assets, structured data, changes since the previous crawl, and technical facts. Following a linked URL opened that URL's page, so normal browser history worked across the investigation. Existing deep links redirected to the new route rather than breaking. The overview grouped its readiness checks in one list. Selecting a severity count opened the matching findings, and the crawl path displayed the recorded internal-link route as a numbered chain. A **Copy for agent** action prepared a prompt with URL context, captured evidence, and the proposed fix for one finding or the current set of open findings. The prompt remained a handoff for review, not proof that the suggested change was correct for every codebase.
New About, Security, and Contact pages
This release introduced dedicated About, Security, and Contact pages. The About page used an interactive, scroll-led story to explain how Contextter connects search evidence, prioritization, and later review. The Security page documented the normal sign-in and workspace access boundaries, stated the limits of those claims, and provided a route for reporting a security concern. The Contact page added a working topic-based form that delivered messages to the team without promising a fixed response time. The pages have continued to evolve since this release, so their current copy remains the authoritative description.
Domain Overview brings key evidence into one snapshot
Domain Overview began combining authority, backlinks, referring domains, estimated organic traffic, ranking keywords, competitors, top pages, anchors, and highly linked pages in one requested snapshot. Before the run, checkout showed the selected market, keyword depth, and estimated price; the final charge stayed within that confirmed estimate. Available history could show monthly traffic and keyword movement, while older analyses remained reachable through pagination. Users could send selected keywords to the Keyword Database or Keyword Research, start a separate analysis from an observed competitor, or compare several domains side by side. A comparison kept authority, traffic, keywords, links, history, gaps, and top pages together and reused recent data where the release contract allowed it. These were dated snapshots and deliberate handoffs, not an automatic import of every observed result.
Workspace home puts current signals before inventory
The redesigned workspace home opened with the signals available for the website: Site Health, average position and its trend, keyword-inventory size, and the number of recorded opportunities. Each summary linked to its underlying view, so a headline number could be checked rather than treated as a complete verdict. The "What to do now" section translated available findings into linked prompts such as reviewing high-severity issues, inspecting a keyword that had dropped, or deciding how to handle recorded opportunities. These were prioritized starting points, not proof that every suggested action would improve performance. Site Audit showed its health indicator, error and warning counts, and frequent findings. Keywords showed position distribution, trend, and the largest movements for a selected list. The Brain and Research widgets summarized the knowledge base and recent reports that belonged to the historical product at this date. Unused tools explained what would appear in their empty area, while a new workspace offered two starting points instead of charts without data. This entry records that dated dashboard, not the current product navigation.
Keyword discovery: pick a depth, not a data source
This release replaced four source-oriented packages with three task-oriented research depths. Quick Research returned related keywords and ideas with their included metrics through the lower-cost route. Deep Research searched more broadly and combined observed Google search suggestions with a metrics check. Competitor Analysis continued to return keywords found for the selected competitor domains. Contextter selected the required sources and removed duplicate candidates before presenting the results. Before each run, the checkout showed the current estimate and available balance. Settlement used the data actually delivered and was bounded by the confirmed estimate. Method cards calculated their estimate from the current seeds, an empty workspace could start from the keywords observed for its own domain, and a "Questions only" filter isolated question-shaped candidates. The Keyword Database also added a direct lookup path. A search for a term not yet stored could create the keyword and open its detail panel; paid metrics appeared only after the user confirmed the data request. These research tiers and prices describe the product at this date. The current checkout remains the authority for today's methods, coverage, and cost.
Optimizer presets now stay in sync
The historical Optimizer began saving the exact strategy and custom focus selected by the user, including rapid consecutive changes. Existing custom presets remained readable, while an invalid stored value returned to a supported default instead of reopening a project with an unsupported strategy or malformed weights. Result warnings were also localized in English, German, French, and Spanish. This entry describes the Writer and Optimizer available at the time, not a current Contextter workflow.
Position Tracking: one surface for rankings, pages, and competitors
This release expanded Position Tracking from a single chart into a dedicated workspace. The overview showed visibility, estimated traffic, average position, the number of tracked keywords in the top 3, 10, 20, and 100, and which terms had entered or left those ranges since the previous measurement. A trend chart covered the selected measurement window. Dedicated views separated the evidence: a position table with movement, search volume, CPC, and the observed ranking URL; a Pages view grouping tracked terms by URL; a Tags comparison for keyword groups; a SERP-features view for recorded featured snippets and AI Overview citations; a competitor comparison using the same keyword set; and a cannibalization report for terms whose observed ranking URL changed between two pages. A context switcher changed device or location across the workspace, while schedule management remained in its own tab. A user could start a schedule by selecting keywords in the Keyword Database and choosing **Track**, without first creating a list. These recurring tracking features describe the product at this date; they are not a promise about Contextter's current feature set.
Research runs now recover more safely
The historical Live Research workflow began validating progress, discoveries, cost, completion, and error updates before they reached the report. An incomplete response ended in an explicit error state instead of leaving malformed report data on the page. A late completion from a cancelled run was also prevented from stopping or overwriting a newer session. The fix reduced a specific stale-update risk in the Research product available at the time; it did not guarantee recovery from every interruption.
A clearer way into the Contextter knowledge system
This release rebuilt the Resources overview and Learning Center as separate entry points for different reading goals. Resources explained the role of the Learning Center, Blog, SEO Glossary, documentation, and Changelog, how they related to one another, and included the blog analyses published at the time. The Learning Center grouped four paths into Keywords and Technical SEO. Each path showed its stated difficulty, estimated duration, and workflow steps, while a goal selector suggested a place to begin. Guides displayed their position in the track and linked to the previous and next path. These were navigation aids, not a claim that the resource set was complete or that one suggested path fit every reader.
A clearer Site Audit and a calmer workspace
This release organized Site Audit around three questions: What did the crawl say about the site's health? Which findings deserve review first? Where did they occur? The overview combined a health score and trend, clickable finding counts, a "Fix first" list, and category tiles that opened the corresponding filtered findings. Sites, Overview, Issues, Pages, Links, Compare, History, Monitoring, and Settings moved into one tab row instead of a second sidebar. Each view opened the latest finished crawl by default. Selecting an older run in the run picker kept a visible route back to the latest result. The Compare tab showed differences between two crawls: findings no longer observed, new findings, and pages added or removed. It documented change between measurements without claiming that a particular fix caused the difference. The application sidebar could collapse to an icon rail with the **[** shortcut. The prepaid balance appeared above the profile, and organization switching moved into the account menu. These navigation details record the interface at this date.
See your site's structure at a glance
The Pages view added a **Site structure** lens beside the flat URL inventory. Its folder tree represented the URLs recorded in the selected crawl. Each folder showed its page count, its share of the crawled site, and how many recorded pages were broken or marked `noindex`. Folders also displayed the open findings for their pages and highlighted those containing critical or high-severity findings. They expanded in place; URL, finding, broken-page, redirect, and `noindex` columns were sortable; and search narrowed the tree without flattening its hierarchy. A folder at any depth opened Page Explorer with a "path starts with" filter already applied. The Pages toolbar kept search and one Filters button visible, with the complete filter workbench and column manager behind that control.
SEO work starts with the task now
This release separated the main SEO jobs in the workspace navigation: Keyword Research for demand discovery, Competitive Research for competitor evidence, Position Tracking for the selected keyword sets monitored at the time, Site Audit for crawl-based technical findings, and the Action Center for prioritization. Keywords remained the shared inventory for lists, filters, Matrix, Kanban, Activity, paid enrichment, and bulk actions. Existing bookmarks continued to resolve to the relevant workflow, while the sidebar and internal links opened each dedicated area directly. The navigation changed without splitting the underlying records. Research results could still be saved to Keywords, tracked lists retained their identity, and recommendations opened the view that owned the evidence or action. The compact sidebar allowed enough room for translated tool labels and kept the complete destination name available to assistive technology. Internal-link opportunities also received one source of record. Site Audit stored the source, target, anchor, and lifecycle evidence in Internal Links. The Action Center could surface prioritized recommendations, but opened the matching filtered Site Audit workbench for the underlying detail. This entry records the product structure at the time, including the historical Position Tracking surface.
A more focused Site Audit workspace
This release narrowed the first Site Audit workspace to crawl setup, health, history, findings, pages, links, monitoring, and settings. Overlapping or unfinished areas were removed from the navigation instead of appearing as if they were ready. Link Explorer remained the dedicated place for site structure and link-path evidence, while the other views stayed focused on the crawl results they actually owned.
Workspace limits explain upgrades and recovery
Workspace creation began explaining directly in the form when the current plan's allowance had been reached. The message showed current usage and the available limit, preserved the user's input, and linked to the relevant plan options without exposing internal error details. Subscription checkout also recognized returning customers whose accounts predated the organization billing model, avoiding a duplicate-customer failure during an upgrade. If a later plan supported fewer workspaces, the release introduced a 30-day adjustment period instead of immediately removing or hiding existing work. Teams could choose which workspaces stayed active and retained read, export, billing, and recovery access for the others. A deliberately deleted workspace remained restorable for 30 days; permanent deletion followed only after the recovery window and a verified cleanup. Organization administrators could also create a private portable export before making the final decision. These were the recovery rules introduced at the time, not a substitute for checking the current plan and retention terms.
Action Center prioritizes the next SEO moves
The Action Center was reorganized around one decision flow: understand the current SEO position, choose the immediate goal, compare prioritized opportunities, and open the specialist view responsible for the selected work. Teams could focus the ranking on balanced priorities, visibility, quick wins, ranking protection, or technical improvements. Each recommendation showed its rationale, intended outcome, estimated effort, and available evidence before the user followed it. The prioritization ranked the evidence Contextter had; it did not guarantee that the proposed action would produce the expected result. On smaller screens, the same decision brief opened in a focused mobile workspace instead of dropping the supporting context.
Keyword intelligence and Site Audit, connected
This release connected the Keyword Database and Site Audit as two parts of the same SEO workflow. A team could move from a search opportunity to the technical findings for an important page, inspect the affected URLs, and compare later crawl evidence with an earlier run. The comparison showed what changed between measurements; it did not prove that one particular intervention caused the change.
Crawl-wide link paths, with their evidence
Link Explorer began using the complete URL inventory recorded for a crawl instead of a small sample loaded into the current view. Selecting a page showed the linking pages and each recorded anchor occurrence. Incoming links, internal and external outgoing links, and self-links stayed separate, with anchor placement and DOM position available as evidence. Pages with many connections opened in a compact cluster view with separate relationship and occurrence totals. A cluster could be expanded into its concrete URLs, while the detailed relationship view remained available. External inbound links were labeled as backlink data from a separate source rather than being inferred from the website crawl.
A clearer command center for SEO work
The workspace dashboard was refocused on the Keyword Database and Site Audit. It brought keyword coverage, search intent, available site-health signals, crawled URL counts, and current priorities into one summary. Each item led to the responsible product area, so the dashboard remained an entry point to the underlying evidence rather than pretending to contain the full diagnosis.
A clearer SEO command center
This companion dashboard update brought Keyword Database and Site Audit summaries into one responsive overview. Key totals, available ranking signals, technical-issue trends, gains, losses, and current priorities could be scanned before opening the underlying workspace. The overview also distinguished current data from unavailable history. An empty chart was labeled as missing evidence instead of implying progress that had not been measured.
Site Audit monitoring alerts are easier to trust
Site Audit monitoring began with simpler recommended presets, while advanced scheduling controls stayed out of the way until someone needed them. Alert history also stopped treating acceptance by the email service as proof of delivery. It distinguished confirmed delivery, bounce, complaint, retry, and a digest still waiting in the queue, so teams could see what was known about a notification instead of assuming it had reached the recipient.
Brief-led content generation
The historical Writer could now begin with the user's brief instead of forcing research to be the first step. It showed whether project knowledge was active and gave explicit directions about exclusions, tone, format, and topic focus priority over generic SEO suggestions. Structure, drafting, and optimization therefore followed the same instruction set from the start. A trust panel made the limits of a draft more visible. It showed when support was missing, evidence was weak, a risky claim had been checked or adjusted, or the Optimizer had drifted from the evidence and user direction. Recurring writing instructions could be corrected, pinned, demoted, or forgotten, while the current project brief could override a saved rule. Before review and scoring, the workflow could remove an unsupported high-risk statement, soften an unsupported absolute claim, or reword it cautiously when the available project knowledge justified that change. Precision edits, Optimizer rewrites, and manual editor suggestions followed the same boundary. They were expected to respect explicit exclusions and avoid introducing concrete claims that the available project knowledge did not support. Quality problems from real runs could be summarized without copying private article text or project knowledge into a report. The safe QA bundle covered weak evidence, unsupported claims, Optimizer drift, ignored directions, and thin topic coverage, and a snapshot could be kept in workspace history. A RAG QA view in the Brain area added a review queue, recurring-pattern summaries, Golden Case drafts, knowledge-connection views, documented browser checks, and calibration packages. A proposed quality change still required explicit review before it could affect live behavior. This entry records the Writer and Brain workflow available at the time; those surfaces are not part of Contextter's current core product promise.
Site Audit foundation for workspace crawls
This release introduced the first workspace flow for a technical Site Audit. A team could add a website, configure the crawl, review the expected use of its prepaid balance, and then start the run. The resulting workspace brought the URL inventory, grouped findings, individual URL evidence, internal links, and the site tree together without presenting the initial foundation as a complete diagnosis of every technical SEO problem.
Keyword discovery, tracking, and reliability
This release connected discovery, stored SERP history, competitor snapshots, score signals, activity history, recurring position checks, and clearer cost feedback inside the Keyword Database. A keyword could move from an initial idea into the monitored set without being copied between separate tools, while paid data actions exposed their cost context more clearly. Recurring tracking described here was part of the product at this date; it is not a promise about the current Contextter feature set.
Keyword workbench visual refresh
The Keyword Database was reorganized for large lists. Metrics, table columns, row actions, and bulk-selection states followed a clearer visual order, so users could compare opportunities without repeatedly losing their place. This release changed the workbench presentation and interaction states; it did not introduce a new keyword metric.
Editorial publishing workflows
Publishing checks for the Blog, glossary, and public service notices became more explicit. Editors could see missing localization, preview an entry, and confirm its publishing state before it reached a customer-facing page. The release did not remove editorial review; it made incomplete translations and readiness problems easier to catch before publication.
Writer, research, and Brain stability
The Writer, Research, and Digital Brain became less prone to state collisions during longer sessions. Saving, restoring, AI-assisted edits, research sessions, and Brain panels handled newer work more carefully when users moved between planning and writing. The update reduced the risk of restoring stale context or overwriting a more recent edit; it did not promise that work could never be lost. These were parts of the historical Writer and Brain workflow available at the time.
Team, billing, and review controls
This release tightened the boundaries between team administration, organization billing, invitations, client access, and editorial review. Account and access changes were handled more consistently, while content and research work moved through a more explicit approval cycle. Teams could tell more easily what was waiting for review and which access or billing context applied before they acted.
Public site and help center refresh
This release repaired inconsistencies across the public website, Help Center, glossary, sitemap, and localized pages. Navigation labels, metadata, translations, and mobile layouts followed the same conventions more consistently, making public routes easier to find and use. It was a presentation and discoverability update, not a claim that every article or translation was complete.
SEO audit and research foundations
This release introduced Contextter's first on-page audit workspace and made partial research data easier to recognize. Reports separated source health, URL-level findings, and missing evidence, so an incomplete dataset was not presented with the same confidence as a well-supported result. Teams could see where the available evidence supported a decision and where another source or a fresh check was still needed.
Dashboard and product controls
Workspace dashboards were reorganized to show more useful status without spreading it across as many screens. Billing state and feature access became easier to distinguish, while the help center was reorganized around onboarding, day-to-day workflows, team use, and troubleshooting. The release changed how existing information was presented; it did not add a new measurement or automated recommendation.
Keyword Database workbench
The Keyword Database brought imports, tags, clustering, requested SERP evidence, detail views, and bulk actions into one workspace. Teams could organize a keyword set before buying additional data, inspect the available competitive evidence, and choose which terms were worth a paid refresh instead of enriching the entire list by default.
Research intelligence and keyword opportunities
The Research view began explaining search intent, topical fit, and missing coverage alongside expanded keyword ideas. Opportunities were grouped into practical labels such as "easy win", "competitive", and "needs more work" so teams could decide what deserved a closer review. The labels were prioritization aids, not promises about ranking or the effort a page would require.
Content guidance and brand voice
The writing workflow could now reuse a stronger brand-voice profile, more relevant internal-link suggestions, and the defaults stored for its workspace. Teams no longer had to restate the same style, quality, and linking instructions whenever they opened a new content project. These were features of the Writer available at the time, not a description of Contextter's current workflow.
Workspace defaults and knowledge intake
New projects could now inherit their target score, author profile, language, and expected word count from the workspace. The website intake used by the Digital Brain was also made more reliable, giving the Writer a more consistent source for brand voice and content guidance without asking teams to re-enter the same settings for every project. These were features of the workflow available at the time.
Team workspaces and EUR billing
This release introduced organizations, roles, invitations, project-level access, and shared billing. Agencies and in-house teams could separate brands or client work inside one workspace structure. Usage was shown in EUR rather than an internal credit unit, making purchase decisions easier to compare with actual spend.
Brain, scoring, and optimization upgrades
The Digital Brain could now connect related facts and favor stronger sources when supplying context to the Writer. Optimization also became section-specific: a weak passage could be revised with the evidence behind that section instead of sending the entire article through a generic rewrite. These functions were part of the Writer and Brain workflow available at the time; this entry does not describe the current product.
Research and content quality foundation
This release introduced the first shared foundation for research-backed content work. The research workflow could bring together signals from search results, community discussions, academic sources, video, and public web pages. A companion score separated relevance, factual support, readability, and basic SEO checks, so teams could see why a draft needed work instead of receiving one unexplained number.
Product interface foundation
This release established the visual system used by the early Contextter interface: higher-contrast surfaces, consistent spacing, shared components, and patterns that also worked in dark mode. Dense SEO data became easier to scan, and moving between projects and the writing workspace involved fewer visual changes.