Your Weekly Feed-Health Routine

A short weekly pass for agencies managing many clients. Work the dashboard's Needs attention queue and project cards, then each affected client's catalog, content and channels, and catch problems before they cost ad spend.

Updated November 6, 2026

Once a week, work from the top down: read the dashboard, open the catalogs of the clients it points at, review their content, then confirm their channels are running. It catches problems before they waste spend, and you never open a healthy account just to check.

The pass at a glance#

  1. Dashboard: read the Needs attention queue, then filter your project cards to Issues and Flagged.
  2. Catalogs: for each affected client, read the catalog's health strip and the warnings on its Activity tab.
  3. Content: review what's waiting on each affected project's Content tab.
  4. Channels: confirm each channel is still Live and its last run succeeded.

Once a month, add a check of every client, described at the end.

Stop 1: The dashboard#

The dashboard, your home page in Renable, rolls up every project in the organization.

  1. Read the Needs attention queue at the top. It lists the organization's open warnings and errors, newest first, as one working list across all your clients. A warning such as Skips 1,204 feed items belongs to a prompt rather than a catalog; see Why a prompt skips some products.
  2. Below the queue, filter your project cards. Issues shows every client with open errors or warnings, and Flagged shows clients with flagged content, meaning content that failed an automatic quality check.
  3. Read each card's signals: its open issues, any flagged content, unpublished drafts, and a freshness line saying import failing or when it last imported, plus how many new feed items arrived this week.
  4. Note the draft reminders below the queue. They call out unpublished changes, such as on a catalog or channel, and inside the project anything with a draft carries an Unpublished badge.
  5. Skim Changes to know about on the right. It lists recent changes worth knowing: what teammates published, content review progress, channels going live for the first time, and unusually large feed changes.

Star your key clients. The dashboard then opens on your starred cards. Stars are personal, so your colleagues' view doesn't change.

Want the full roster instead? The Projects list shows every project, with an Attention column giving the same issues and flagged content per row. Show archived adds archived projects.

Stop 2: Each affected catalog#

For every client that showed a signal, check that the feed is importing cleanly.

  1. Open the project, then open the catalog from its Catalogs tab.
  2. Read the health strip at the top of the catalog page. A healthy feed shows a green light, a recent time such as Last import 25 minutes ago, and the product count. A problem shows something like Needs attention — 3 warnings.
  3. Open the Activity tab to see what each import did and read the warnings under it. A warning that hit 500 products is one line, and you can open it to see them.

Reading a run's statistics, tracing a value and what each warning means are covered in Imports, warnings, and tracing a value.

A client suddenly went quiet, with no imports at all? Two things stop a whole account rather than one feed. Open the Projects list with Show archived on, because archiving a project archives every catalog inside it. Then check the organization's subscription, since a lapsed one empties the feeds until it's reactivated. If neither applies, the catalog's import history says what happened.

Stop 3: Content awaiting review#

Unapproved content ships to your ads by default, so review what matters most.

  1. Open the project's Content tab.
  2. Scan the approval status per product. Gallery view is quick for images, and table view lets you move through rows with the review hotkeys.
  3. Approve what looks right.

Hotkeys and bulk actions are in Reviewing and approving content. For many accounts in one sitting, use Review content quality across many clients.

Stop 4: Channel status#

Last, confirm each channel is still running and uploading its feed.

  1. On each affected project's Overview, read the channel cards. Each shows Live, Preparing, or a color-coded count of open channel events. Open any channel that stopped uploading, whose last run failed, or whose publish a monitor is holding.
  2. Open the channel's Activity tab to see each run's status, counts and any required-field warnings. A run a monitor held shows Publish held, and the previous feed stays live meanwhile.
  3. If runs succeed but the destination still doesn't accept the products, the rejection is usually on its side. See Fix products disapproved by Google.

Once a month: check every client#

A catalog that stops importing raises no warning of its own, so it can hide behind a clean-looking card. Its only sign is a last-import time that keeps getting older, while a healthy feed's stays within about the last hour even when nothing changed.

Open the Projects list and read the Last import column for every client. That column shows a project's newest import, so in a project with several catalogs, check each catalog's health strip too.

To be told instead, set up a monitor: the Feed hasn't updated in a while suggestion on the Monitoring page does it.

Or ask Aimée#

Ask Aimée "Why isn't this product in my feed?" and she follows that one product end to end and tells you which step dropped it. She can also take two parts of this routine off your hands:

  • Investigate a warning. Every warning on the Activity tab has an Ask Aimée to investigate action. One click and she looks into what caused it and what to do about it.
  • Wait for an import. After you publish a fix, ask her to wait for the import to finish and report the real counts and warnings.

FAQ#

I manage 40 clients. Do I really open every one each week?

No. The dashboard shows the clients that need you, and a client with no signal usually doesn't need a weekly visit. The monthly check catches a catalog that has stopped importing.

A warning says it affected hundreds of products. Do I fix each one?

No. Fix the cause once, at the source feed or with a single rule that covers the whole group. See Bulk-fix a whole category with one rule.

I fixed something last week but it never took effect. Why?

Check for an unpublished draft first. Edits to a catalog or channel wait until you Publish, and imports use your last published configuration. The dashboard's draft reminders are there to catch this.

Related articles#