<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://www.mundaneadventures.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=JulianDeasey465</id>
	<title>WikiName - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://www.mundaneadventures.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=JulianDeasey465"/>
	<link rel="alternate" type="text/html" href="https://www.mundaneadventures.com/index.php/Special:Contributions/JulianDeasey465"/>
	<updated>2026-11-12T10:30:24Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.46.2</generator>
	<entry>
		<id>https://www.mundaneadventures.com/index.php?title=How_Perplexity,_ChatGPT_And_Gemini_Pick_Their_Sources&amp;diff=31508</id>
		<title>How Perplexity, ChatGPT And Gemini Pick Their Sources</title>
		<link rel="alternate" type="text/html" href="https://www.mundaneadventures.com/index.php?title=How_Perplexity,_ChatGPT_And_Gemini_Pick_Their_Sources&amp;diff=31508"/>
		<updated>2026-08-17T19:14:57Z</updated>

		<summary type="html">&lt;p&gt;JulianDeasey465: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Write it once, covering the category question, the problem question, the comparison question, the competitor question and the branded question. Fifty is a workable minimum. Then freeze it, and if you must add prompts later, add them as a separate cohort so the original series stays comparable.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;If you must change the prompt set, add new prompts as a separate cohort and keep the original series running unchanged. Editing the instrument retrospectively destroys the comparison you have been building.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Tracking this is genuinely awkward, and pretending otherwise is how most reporting in this field goes wrong. There is no console. Answers vary between runs. Referral attribution is inconsistent between assistants. Anyone handing you a single confident number has hidden a great deal of variance behind it.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Observed behaviour leans toward breadth, pulling from a wider set of sources per answer than the others, and it cites forums, documentation and niche trade sources readily. It also appears comparatively responsive to freshness.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;The important detail is that this does not replace the results page, it displaces it. Your listing is still there. It is simply lower down the screen and competing with an answer that has already satisfied a portion of the audience.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Also decide up front who owns this. Measurement that belongs to everyone gets run inconsistently, the conditions drift, and the series becomes uncomparable within two quarters. One named person running a modest set reliably produces more usable information than a sophisticated programme with no owner.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Third, and least comfortable, reduce dependence on this one channel. Brands that were already visible through communities, direct relationships, email and their own reputation have absorbed the change far better than brands whose entire acquisition rested on informational search traffic.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;One scheduling detail improves comparability more than it should. Run on roughly the same date each month rather than whenever somebody remembers. Retrieval behaviour and the freshness of competing sources both vary over a month, and a series taken at irregular intervals introduces variation that looks like a trend.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Equally, do not restructure an entire site on the assumption that all informational content is now worthless. The impact is concentrated in a specific type of query. Measure which of your pages carry the signature before reacting, because the temptation to attribute every traffic decline to this is strong and often wrong.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Testing too rarely means you find out about a problem a quarter after it started. Testing too often means drowning in variance that looks like signal and reacting to noise. Both failures are common and the second is more expensive, because it produces work.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Ahrefs measured the overlap in July 2025 across 15,000 long-tail prompts and four assistants, finding roughly 80 percent of cited pages did not rank for the original query at all. Ranking gets a page considered. It does not reserve a seat.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;What Kind of Content Lost the Most The pages that suffered most are the ones whose entire value was a fact a summary can state. Definition posts, unit conversions, simple how-to answers, opening hours, basic specifications and the introductory paragraph content that many sites published purely to capture a query.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;On Third Party Tracking Tools Several tools now offer to monitor this at scale, and they save real time once your prompt set runs into the hundreds. They are worth buying for trend lines and for coverage you cannot manually sustain.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Watch the source list as closely as the mention rate, because it usually moves first. New citations from a directory you corrected are a leading indicator, and they typically appear a month or two before any change in whether you are recommended.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Starting With Content The most common and the most expensive. A brand decides to take this seriously and commissions twenty articles, without knowing which questions matter, which assistants answer them badly, or which sources those answers are built from.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Gemini and Google Surfaces Closest to conventional search infrastructure, which has a practical consequence: work that improves your standing in Google search tends to carry over here more than it does elsewhere.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;The specific damage is that somebody sees a dip, rewrites a page, sees the number recover for unrelated reasons, and concludes the rewrite worked. That false lesson then gets applied elsewhere. A slower cadence with more runs per prompt is more informative than a faster one with fewer.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;If your organic impressions held steady while clicks fell, you have probably met this already. An AI generated summary now sits above the results for a large share of informational queries,  [https://www.88pianists.com/ llm seo] answers the question in place, and leaves the ten blue links below it with less to do.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Two implications follow regardless of which system you are studying. Being findable by the underlying search step is necessary, and being worth quoting once fetched is what decides whether you are used. Almost everything actionable sits in those two requirements.&lt;/div&gt;</summary>
		<author><name>JulianDeasey465</name></author>
	</entry>
	<entry>
		<id>https://www.mundaneadventures.com/index.php?title=User:JulianDeasey465&amp;diff=31507</id>
		<title>User:JulianDeasey465</title>
		<link rel="alternate" type="text/html" href="https://www.mundaneadventures.com/index.php?title=User:JulianDeasey465&amp;diff=31507"/>
		<updated>2026-08-17T19:14:52Z</updated>

		<summary type="html">&lt;p&gt;JulianDeasey465: Created page with &amp;quot;41 years old Accounting Assistant IV Allene Murphy, hailing from Shediac enjoys watching movies like &amp;quot;Edward, My Son&amp;quot; and Coloring. Took a trip to St Mary&amp;#039;s Cathedral and St Michael&amp;#039;s Church at Hildesheim and drives a Ferrari 250 GT LWB California Spider.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Check out my web blog :: [https://www.88pianists.com/ llm seo]&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;41 years old Accounting Assistant IV Allene Murphy, hailing from Shediac enjoys watching movies like &amp;quot;Edward, My Son&amp;quot; and Coloring. Took a trip to St Mary&#039;s Cathedral and St Michael&#039;s Church at Hildesheim and drives a Ferrari 250 GT LWB California Spider.&amp;lt;br&amp;gt;&amp;lt;br&amp;gt;Check out my web blog :: [https://www.88pianists.com/ llm seo]&lt;/div&gt;</summary>
		<author><name>JulianDeasey465</name></author>
	</entry>
</feed>