--- title: "Run cross-functional SEO meetings that end in owned, dated decisions" description: "Agendas for weekly, monthly, quarterly, and technical SEO meetings with content, engineering, and product, plus decision roles and action rules." canonical: "https://scalewithsearch.com/articles/cross-functional-seo-meetings" date: "2026-03-20" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Run cross-functional SEO meetings that end in owned, dated decisions. Developers wait for a content brief. Writers wait for keyword research that the SEO specialist has not delivered. A product change ships without anyone checking its effect on search. Every group is busy, and the SEO initiative sits between them. Cross-functional SEO meetings coordinate SEO specialists, content creators, developers, product managers, and marketing leaders on work that needs more than one discipline. Many of these meetings waste time on status updates, open brainstorming, or technical detail that loses half the room. An effective meeting has an owner, a decision-maker, and action items with names and dates. Its measure is not attendance or discussion quality. It is the number of initiatives that ship and move rankings and traffic. ## Match the meeting to the job | Meeting | Purpose | Attendees | Length | Success | |---|---|---|---|---| | Weekly operations sync | Coordinate execution, remove blockers, track active work | SEO lead, content lead, development lead | 30 minutes | Clear next actions, blockers resolved or escalated, no surprise delays | | Monthly strategy review | Judge what worked, adjust priorities, set next month's focus | SEO lead, content manager, engineering manager, product manager, marketing director | 60 minutes | A ranked roadmap, committed resources, agreed success metrics | | Quarterly planning | Set objectives and key results (OKRs), allocate budget, align with business goals | SEO lead, VP Marketing, VP Engineering, VP Product, content director | 90 to 120 minutes | Approved OKRs with executive support, committed resources, named owners | | Technical working session | Solve one technical problem in depth | SEO technical lead, senior developers, sometimes a product manager or architect | 60 to 90 minutes | An agreed approach, a written plan, an owner with a deadline | For how OKRs for search get written, read [SEO OKRs for executives](/articles/seo-okrs-executives). ## Run the weekly operations sync | Item | Minutes | Content | |---|---|---| | Content status | 5 | Articles published last week, articles due next week, blockers to publication | | Technical status | 5 | Structured data deployed, Core Web Vitals work in progress, technical debt that affects SEO | | Performance check | 5 | Traffic trend against last week, ranking changes for priority keywords, critical issues | | Blockers | 10 | Resolve what the group can; escalate what needs a leadership decision | | Action items | 5 | Confirm next week's commitments, owners, and deadlines | ## Run the monthly strategy review | Item | Minutes | Content | |---|---|---| | Performance | 15 | Organic traffic and revenue trends, ranking gains and losses, competitive position, content highlights | | Strategy assessment | 15 | What worked, what did not, and whether resources went to the right work | | Competitive intelligence | 10 | Competitor content and technical changes, market shifts, new opportunities or threats | | Next month | 15 | The top 3 to 5 initiatives, the resources they need, expected outcomes and metrics | | Dependencies | 5 | Engineering needs, content needs, product changes that affect search | ## Run the quarterly planning session | Item | Minutes | Content | |---|---|---| | Retrospective | 20 | OKR results, return on major initiatives, lessons and process changes | | Business context | 15 | Company goals, the product roadmap as it affects search, marketing priorities | | Search landscape | 15 | Algorithm updates, competitive position, quantified opportunities | | OKR proposal | 20 | Proposed objectives and key results, headcount, budget and tools, dependencies and risks | | Cross-functional capacity | 15 | Engineering capacity for SEO, content capacity, product requests that affect SEO | | Budget and resources | 15 | Tool renewals, content production budget, contractor or agency needs | | Next steps | 10 | Action items and owners | ## Call a technical working session when a problem needs depth Some problems do not fit a status meeting. Examples are JavaScript SEO for a React application and crawl budget on a large site. A URL structure for a new product section, a broken canonical setup, and structured data at scale fit here too. Give each one its own session in four parts: 1. Define the problem and its context (10 minutes). 2. Explore the technical options (30 minutes). 3. Design the solution and name its trade-offs (20 minutes). 4. Write the implementation plan and timeline (10 minutes). Keep these sessions separate from the cross-functional meetings. In the cross-functional meetings, translate technical detail into business impact. ## Prepare before the meeting Send the agenda 24 hours ahead. State the meeting objective, the decisions the group must make, the pre-read, and what each attendee must prepare. An example pre-read for the monthly review contains four items: - last month's traffic report from Google Analytics; - ranking changes for tracked keywords, exported from Ahrefs; - the list of published content with its performance; - a short competitive summary of 2 or 3 points. Attendees who arrive informed do not spend the meeting on context. Time-box each agenda item, and show a visible timer. Keep a parking lot document for ideas that matter but do not belong on today's agenda. A facilitator can say: "Let's put the URL migration in the parking lot for the next technical session." That acknowledges the idea and keeps the meeting on its agenda. ## Assign decision roles with RAPID RAPID, a decision framework from Bain & Company, gives each person one role: | Role | Who, in an SEO decision | |---|---| | Recommend | The SEO team proposes the solution | | Agree | Development and content teams confirm the approach is workable | | Perform | The implementation owners execute | | Input | Stakeholders contribute expertise | | Decide | One final decision-maker, usually the marketing director or a VP | An example: the SEO team recommends a move of the blog from a subdomain to a subfolder. Development agrees on the implementation approach, and a developer performs the migration. Product and content give input on the user impact. The marketing director decides go or no-go. With the roles set, nobody asks "who decides this?" For a standing map of these roles across all SEO work, read the [SEO responsibility matrix](/articles/seo-responsibility-matrix). ## Write action items that get done Every action item carries four fields: - one owner, a named person, never "the team" or "someone"; - a specific date, never "soon"; - a definition of done; - a priority: P0 for a blocker, P1 for important, P2 for nice to have. A weak action item reads "Update meta descriptions." A strong one reads: "The content lead updates the meta descriptions for the top 20 traffic pages to the new voice guidelines. Done when all 20 are deployed. Due March 15. P1." ## Pair SEO with content, engineering, and product **SEO and content** meet weekly for 30 minutes or every two weeks for 45. The agenda has four items. First, the performance of articles published 30 to 90 days ago, with high performers to expand and weak ones to diagnose (10 minutes). Second, articles in production, writer questions, and whether the briefs are clear enough (10 minutes). Third, keyword research, topic priority, and brief assignments for the next cycle (15 minutes). Fourth, process improvements, pain points, and template changes (10 minutes). The group decides the next keywords, the order of work in production, and changes to the brief template. **SEO and engineering** meet every two weeks for 45 to 60 minutes. Start with a technical health check: Core Web Vitals, crawl errors, indexing, speed, and mobile usability (15 minutes). Review active projects, new obstacles, and testing status (15 minutes). Then weigh new initiatives with their business case, effort estimate, and priority against other engineering work (15 minutes). Close with developer questions: SEO needs for upcoming features, recent deployments that affect search, and how search engines behave (10 minutes). The group decides what enters the next sprint and the technical approach. To earn engineering time in the first place, read [engineering buy-in for SEO](/articles/engineering-buy-in-seo). **SEO and product** meet monthly for 45 to 60 minutes, or before a major release. Review the roadmap for features, new page types, and URL changes that affect search (15 minutes). Look for search opportunities: features that solve searched problems, content ideas from product data, and user-generated content (15 minutes). Check current joint work and product pages that perform well or poorly in search (10 minutes). Finish on positioning and competitor features worth highlighting (10 minutes). The group decides the SEO requirements for launches, the URL structures for new sections, and the priority of SEO-related features. ## Fix five meeting failures **Status-update meetings.** Attendees take turns with reports, and the meeting makes no decisions. Move status to email or a dashboard before the meeting. Open with: "Everyone has read the updates. Any questions before we move to decisions?" When someone starts a status report, redirect: "I saw that in your update. Let's discuss the blocker you mentioned." Use the time for blockers, decisions, and strategy. **Open brainstorming.** A session produces dozens of content ideas with no priority and no follow-through. Constrain it. Cap it at 5 to 10 ideas, and require keyword research before the meeting. Score the ideas on the spot, and assign owners before the meeting ends. **Technical detail that loses the room.** Developers and SEO specialists go deep while content and marketing attendees disengage. Move deep dives to technical sessions with technical attendees only. Translate technical points into business impact, and send technical context as pre-reading. **No follow-through.** A good discussion leads nowhere. Reserve the last 5 to 10 minutes for action items in a shared document everyone can see. Confirm each owner and date. Send the notes right after the meeting, and open the next meeting with the previous action items. **Too many meetings.** A weekly meeting has too little to decide. Audit each recurring meeting every quarter. Cancel any meeting where half the time is "no updates." Merge low-value meetings into one monthly check-in, and move coordination to Slack or email. ## Adapt for remote and async teams Collect input before the meeting. Share a document with the questions, and give attendees 48 hours to answer in writing. The meeting then discusses where views differ, instead of gathering information. An example: for the monthly review, everyone adds "what worked" and "what did not" to the shared document in advance. The meeting debates the themes and decides, and it can run shorter. Record every meeting in Loom, Zoom, or Google Meet for people who cannot attend. Store recordings with searchable titles, and put timestamps for key decisions in the notes. Use one notes template: ```text Meeting: [name] Date: [date] Attendees: [names] Recording: [link] Key decisions 1. [decision, with context and implications] Action items - [action]. Owner: [name]. Due: [date]. Priority: [P0/P1/P2] Discussion summary [short summary of the main points] Next meeting Date: [date] Pre-read: [what to review first] ``` For global teams, rotate meeting times each quarter so that one time zone does not always carry the late call. Put the most important meetings in shared working hours. Use async processes where they work, and document thoroughly. ## Measure whether the meetings work Track four measures: - implementation rate: the share of action items completed on time, with a target of 80 percent or more; - attendee rating each quarter: a 1-to-5 score for purpose, a check on frequency, and whether each attendee still needs a seat; - decision speed: the time from decision to implementation, and the number of meetings a decision takes; - business impact: whether the initiatives that planning prioritized moved traffic and revenue, and whether meeting time matches strategic importance. An implementation rate below 60 percent points to unrealistic commitments or weak accountability. ## Handle the hard cases **Busy executives.** Frame the quarterly session around business outcomes, not SEO tactics. Send a pre-read that shows revenue impact with specific examples. Limit executive time to strategic decisions: budget, priorities, and resources. Let them delegate the tactical parts, and move through the agenda fast. For the reporting format, read the [executive SEO reporting template](/articles/executive-seo-reporting-template). **Developers with no time.** State the impact in the terms engineering leaders use: revenue at risk, competitive threats, and user experience problems. Show the traffic and conversion data behind the request. Start with small wins that need little engineering effort, and build credibility before you ask for a large investment. **No authority over attendees.** Work through influence. Show value with data and results, and build relationships with the functional managers. Use RAPID so that decision rights are explicit. Escalate stalled coordination to shared leadership. Frame requests around shared goals such as revenue and user experience, not "SEO needs." For how a technical leader weighs such requests, read [how a CTO evaluates marketing SEO requests](/articles/cto-evaluate-marketing-seo-requests). **Every meeting that mentions search.** An SEO specialist does not need to attend all of them. Attend where SEO expertise is needed for a decision. Decline meetings where you are informed only. Ask to be consulted async, or invited when a specific topic comes up. Spend the saved time on high-impact work. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```