Skip to content

Library, publishing, indexing, and citations

Copy for agent Copied

The Library in Content → My Content is the working list of briefs and articles for the selected project. It lets you find a saved brief, continue an article, record where you published it, check its indexing state, and see whether AI answers cite the live page.

The library is shared by people who have access to the selected project. It includes articles created by other project members, so a team can review publishing and citation progress together. The person who created an article remains recorded as its author. Other project members can open it to review the content, while changes to the article and generating an article from a brief remain limited to its creator. Items cannot be deleted from the library.

The status tabs filter the library by All, Brief, Draft, Ready, Published, and Tracked. A brief is a saved plan awaiting article generation or handoff; a draft is generated or edited content still being worked on; Ready marks content prepared for the publishing workflow; Published and Tracked are later states in the live-page workflow. Processing or error states can also appear while generation is running or after a failed operation.

Status is not the same as indexing state. An article’s workflow status describes where the content sits in your editorial process. The indexing filter describes the state of its public URL:

  • Indexed means an indexed time is recorded.
  • Submitted means a request was sent and an indexed time is not yet recorded.
  • Not indexed means it has not been recorded as indexed and is not currently shown as submitted.

The table also provides search over the article name and linked prompts. Use the status and indexing filters together to find, for example, published articles awaiting indexing or briefs for a specific prompt. Column sorting and pagination help when the library grows; the table displays ten rows per page.

  • Name identifies the brief or article.
  • Linked to shows the target prompt the piece is intended to address. The relationship gives later visibility and citation measurements a specific question to refer to.
  • Status shows the workflow state described above.
  • Published shows the recorded publication date when available. Adding a URL is separate from publishing the article itself.
  • Indexed shows the recorded indexing state and date. A page must be indexed before it can be cited, but indexing alone does not make a citation happen.
  • Citations counts AI answers that currently cite the piece and can show a trend against the previous period when the underlying data is available.

The card summary states how many live pieces are cited out of the live pieces it counts. In the current table, live pieces are those with Published or Tracked status. This is a useful overview, not a citation rate for all drafts or briefs.

Select a row or Open to view a brief or article in its editor. A published URL can be opened in a separate browser tab with Open live. If you have write access and the item is in an eligible state, use Add URL, Publish, or Edit URL to record or update the destination.

The library export menu offers CSV, Excel, and Markdown. Export uses the rows currently shown after applying status, indexing, and search filters. It exports the library table fields: name, linked prompts, status, publication date, indexing date, and citation count. It does not export the full article body or the brief document. Use the editor’s download and brief export controls for those files.

PromptEye does not publish the article to your website from this action. Publish the content through your CMS or normal publishing process, then select the article in the library and add its public URL. The form accepts a valid HTTP or HTTPS address. After saving, the article record can attach indexing and citation signals to that destination.

For a Ready, Published, or Tracked item, you can edit the saved URL. Confirm that the URL points to the actual article page, not a homepage or preview. If the public address changes, update the record so future checks use the current page. Saving the URL changes the PromptEye record; it does not move, redirect, or edit the website page.

If more than one eligible article needs a URL, the publish dialog lets you choose the item. Verify the article name before saving. This avoids attaching one page’s live URL to the wrong brief or draft.

A published or tracked item with a public URL can be eligible for an indexing request when it has not already been recorded as indexed or submitted. Use the row action to request one URL. The table also offers Request indexing (N) for eligible visible rows matching the current filters. Review the count and filtered rows before using the batch action.

PromptEye submits the indexing request and later checks whether Google has picked the page up. The first check runs about a week after the publication date, and then once a week until the page is indexed. Submitted is confirmation that a request was sent; Indexed is a later result. If a page is still not indexed about three weeks after the request, a recommendation flags the delay. A request does not guarantee Google will index the page, how quickly it will do so, or whether an AI answer will cite it. If a request fails, the interface reports that it could not be sent. Confirm the live URL and project access, then retry when the action is available.

If the row shows Not indexed, this does not prove the page is permanently excluded. Confirm that it is publicly reachable and that the correct URL is saved. If an indexing recommendation says a submitted request has stalled, inspect the live page and check it manually. The request action is not a substitute for fixing a page that returns an error or is blocked.

The citation column shows how many AI answers currently cite the live piece. The library may show a trend against the previous period. Open the target prompt and its citation results when you need to see which model or response used a page and what other sources appeared.

A citation is evidence that the source page appeared in an answer captured by PromptEye. It does not establish how many people read that answer, whether the answer led to a visit or sale, or whether the article alone caused a change. Compare the cited page, target prompt, answer, source list, and time period before deciding what to update next.

The loop suggests that citation evidence can feed back into recommendations. A cited article may become a candidate to refresh or expand; an article with no citations may prompt a review of prompt fit, crawlability, source material, or coverage. The recommendation is a next-step suggestion, not an automatic conclusion that a page is good or bad.

Submitted means the request was sent. PromptEye checks for an indexed result about a week after publication and then weekly, but Google decides when or whether it indexes the page. Check that the public URL works and allow time for a result.

Does adding a URL mean the article is published?

Section titled “Does adding a URL mean the article is published?”

No. It records a URL in PromptEye after you publish through your own CMS or website process. The action does not upload article text or change your site.

The item may be a brief, draft, or ready article without a public page, may not have a valid URL, or may already be indexed or submitted. Indexing requests apply to eligible published or tracked items with a live URL.

Only the visible library fields for rows matching your current filters and search. Use the editor’s export for the brief or article content itself.

Does Tracked mean the article has citations?

Section titled “Does Tracked mean the article has citations?”

No. Tracked is a workflow status. Citation count is a separate column and may be zero even for a tracked article.