Weekly email digest

What the email contains

• Brand mentions: the week's total, compared with the previous week, with the gap.
• Competitors gaining and competitors declining: the three biggest moves on each side.
• New cited URLs: the sources that appeared in AI answers this week.
• Recommendations: the priority actions of the moment, each with its link.
• Google Business Profile: for a project that has a listing, a block covers the week's figures, new reviews and negative ones left unanswered for more than 48 hours.

When it goes out, and to whom

• Sent automatically on Monday from 9 a.m., Quebec time, by PivotSEO's internal scheduler — no external cron is required.
• One send per day at most, and no catch-up: a digest several days late is of no interest to anyone.
• The recipient is the address of each project's owner.
• The email belongs to the plans that include reports: an account without that option does not receive it, and the diagnostic says so.
• Anyone who unsubscribed is permanently excluded; every email carries its own one-click unsubscribe link.

Checking before you send

• Generate preview builds the current week's digest for the selected project: period covered, indicators, competitors, URLs, recommendations.
• Further down, a rendered HTML preview shows the email exactly as it will land in the recipient's inbox.
• Send the digest now ships it to an address of your choice: do this before letting it go out to a client.

The three cards at the top

Cadence recalls the schedule and the date of the last successful send. Email service is a diagnostic: sending service configured or not, sender address, how many projects are ready to receive the digest and how many are waiting for an address — addresses are partly masked there, and the card is reserved for administrator accounts. Test before sending simply restates the procedure.

Nothing is being sent

If the Email service card reports that the sending service key is not configured, nothing will go out, neither automatically nor on demand: that configuration lives on the server, not in the interface. The preview keeps working regardless — it depends on no send.