<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Querytally</title>
    <description>The latest articles on DEV Community by Querytally (@querytally).</description>
    <link>https://dev.to/querytally</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4243641%2F8bd8b3cf-5fd2-4506-8af9-39ba47d885d4.png</url>
      <title>DEV Community: Querytally</title>
      <link>https://dev.to/querytally</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/querytally"/>
    <language>en</language>
    <item>
      <title>Your agent can write the page. It can't know what people search for.</title>
      <dc:creator>Querytally</dc:creator>
      <pubDate>Fri, 13 Nov 2026 22:59:05 +0000</pubDate>
      <link>https://dev.to/querytally/your-agent-can-write-the-page-it-cant-know-what-people-search-for-551d</link>
      <guid>https://dev.to/querytally/your-agent-can-write-the-page-it-cant-know-what-people-search-for-551d</guid>
      <description>&lt;p&gt;An agent will write any page you ask for. It will also invent the reason the page should exist. Ask it which pages your site needs and you get a confident list with no numbers behind it.&lt;/p&gt;

&lt;p&gt;The fix is to hand the agent real searches and make it work from them. Below: the brief to give it for each page, the order to publish in, and what to check after 28 days.&lt;/p&gt;

&lt;h2&gt;
  
  
  What goes in a page brief
&lt;/h2&gt;

&lt;p&gt;One page answers one group of searches. The brief holds five things:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;The searches the page answers, with how many people in the US make each one a month. Real numbers, not the agent's guess.&lt;/li&gt;
&lt;li&gt;The intent. Does the searcher want to buy, compare or learn? A buying search gets a short page with a clear next step. A learning search gets an explanation. (More on reading intent: &lt;a href="https://querytally.com/search-intent/" rel="noopener noreferrer"&gt;search intent&lt;/a&gt;)&lt;/li&gt;
&lt;li&gt;One competitor page that already answers it, as a link. The agent reads it and has to add one thing that page lacks.&lt;/li&gt;
&lt;li&gt;Where the page sits: its hub, and the two or three pages it links to and from.&lt;/li&gt;
&lt;li&gt;What a visitor does next: the one action the page asks for.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Put those five lines above your prompt and the draft changes. The agent stops padding, because it knows who is asking and what they want.&lt;/p&gt;

&lt;h2&gt;
  
  
  Publish fewer pages, in this order
&lt;/h2&gt;

&lt;p&gt;Start with the searches closest to a sale, then the comparisons, then the explanations. Publish a hub with at least three pages under it, never a lone page. On a new site, a few pages a week is plenty. Fifty pages in a day is how a site gets ignored.&lt;/p&gt;

&lt;h2&gt;
  
  
  Check each page after 28 days
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;Is it indexed? If not, link to it from the hub and from one strong page.&lt;/li&gt;
&lt;li&gt;Is it shown for the searches in its brief? If it's shown for different ones, rewrite the title to match those.&lt;/li&gt;
&lt;li&gt;Does anyone click? If it's shown and not clicked, fix the title and the description before touching the page.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Where the searches come from
&lt;/h2&gt;

&lt;p&gt;The first line of the brief is the part an agent can't make up. Querytally sends it as a finished content plan: each page with its US monthly searches, its intent and the competitor page that already has it. There is a free sample by email within 24 hours: &lt;a href="https://querytally.com/site-structure/content-plan/" rel="noopener noreferrer"&gt;content plan sample&lt;/a&gt;&lt;/p&gt;

</description>
      <category>seo</category>
      <category>webdev</category>
      <category>agents</category>
      <category>productivity</category>
    </item>
  </channel>
</rss>
