M-17-06 made federal websites checkable from outside: set addresses, shared analytics and GSA approval of .gov
OMB’s November 8, 2016 memo told agencies to publish pages at set addresses, run GSA’s analytics code and use approved .gov domains. A 2023 memo rescinded it but kept the privacy page and shared analytics; later orders turned to design and one front door.
Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.
Two-minute summaryThe dek and the first sentence of each section, quoted from the article
OMB’s November 8, 2016 memo told agencies to publish pages at set addresses, run GSA’s analytics code and use approved .gov domains. A 2023 memo rescinded it but kept the privacy page and shared analytics; later orders turned to design and one front door.
- The week It listed what the public used them for.
- Set addresses: pages every agency had to publish at the same place M-17-06 used a simple device.
- Shared measurement: one analytics code, one search duty and a public dashboard One shared code does two things.
- The domain as a gate: .gov approval, migration and the registry of accounts Section 9 turned the domain into an enforcement point.
- What stayed inside: platforms, records, information quality and privacy notices The memo pointed to a list of tools with federal-compatible terms of service, and to M-13-10 on Antideficiency Act issues in online terms. [1] It required a careful privacy analysis under M-10-23 for third-party sites. [1] An outsider could confirm none of them.
- How the memo landed on different public bodies A department with dozens of component sites faced the memo at scale.
- Objections, in order The objection is that a required page at a required path invites agencies to publish something, anything, at the path.
- What CIOs and digital directors could check The memo has been rescinded, as the hindsight section explains.
- With hindsight Part of the substance had already moved into law.
The week
On November 8, 2016, the Office of Management and Budget issued Memorandum M-17-06. [1] Its subject was policies for federal agency public websites and digital services. [1] The memo opened by calling those websites and services the primary means by which the public receives information from the government and interacts with it. [1]
It listed what the public used them for. People applied for benefits, searched for jobs, complied with federal rules and found authoritative information there. [1] OMB said the sites should meet and maintain high standards of effectiveness and usability, with quality information readily accessible to all. [1]
M-17-06 placed itself in a line of earlier policy. It said it built on the Digital Government Strategy of May 23, 2012, and on the U.S. Digital Service Playbook, released on August 11, 2014, with 13 plays. [1] It said its goals aligned with M-11-24 on service delivery and M-10-06, the Open Government Directive. [1] It rescinded and replaced M-05-04, OMB’s earlier policy for agency public websites. [1]
The memo defined its scope broadly. Public websites and digital services were online information resources or services maintained in whole or in part by executive branch departments and agencies. [1] The definition covered services operated by an agency, by a contractor, or by another organization on the agency’s behalf. [1] A footnote said digital services included websites, mobile applications and social media, and transactional services such as online forms and benefits applications. [1]
The timetable was short. Unless existing law or policy already required something, or the memo said otherwise, agencies were expected to comply within 180 days of its publication date. [1] Some items had their own clocks. Agencies had 60 days to update their list of non-government web addresses and 60 days to register public accounts with the U.S. Digital Registry. [1] They had 18 months to bring their privacy pages into full compliance on system of records notices. [1]
OMB gave the General Services Administration two jobs in the memo. GSA would regularly report on its DotGov Dashboard how agencies were implementing the policies. [1] And GSA’s Office of Government-wide Policy would stand up a new council of agency web and digital directors within 30 days. [1]
The body of the memo ran to 18 numbered sections. They covered digital governance, analytics and user feedback, search, open data, access on multiple devices, privacy, security and privacy controls, and secure connections. [1] They also covered approved domains, third-party websites, information quality, accessibility, records management, plain writing, multilingual content, mandatory links, IPv6 and a consistent look and feel. [1]
Several sections set out specific public addresses. Each agency was to post its digital governance plan at www.[agency].gov/digitalstrategy. [1] It was to publish a machine-readable data listing at www.[agency].gov/data.json and a human-readable one at www.[agency].gov/data. [1] Its web programming interfaces and documentation were to sit at www.[agency].gov/developer. [1] Its privacy program page was to be at www.[agency].gov/privacy, reachable from the agency’s About page. [1]
Other sections set measurement and security duties. All agencies had to join GSA’s Digital Analytics Program and deploy its tracking code on all public-facing websites. [1] The memo restated the existing requirement that all existing federal websites and services be reachable through a secure connection by December 31, 2016. [1] New sites had to meet the HTTPS policy at launch. [1]
The domain section was firm. New executive branch .gov domain names needed approval from GSA’s Office of Government-wide Policy. [1] That office could deny new requests or renewals for agencies that could not show reasonable compliance with the memo’s policies. [1] Agencies were to move official public sites onto .gov or .mil domains within 180 days, unless the agency head explicitly decided a non-government domain was necessary. [1]
The memo closed with the standard statement that it created no right or benefit enforceable at law against the United States or its agencies. [1] Its practical force, in our reading, came from GSA’s role over the domain and the public reporting the memo described.
M-17-06 has the look of a checklist. Eighteen numbered sections, most with lettered items, cover everything from search boxes to IPv6. [1] Read as a whole, though, the memo did something more specific. It made a large part of an agency’s web obligations testable by someone outside the agency.
Our argument is that M-17-06 converted website quality from an internal judgment into a set of outside checks. A visitor, GSA, an inspector general or a journalist could test them without asking the agency for anything. The memo did this through set addresses, a shared measurement tool and control of the domain. [1] What it could not make checkable from outside, it left to internal records that only an audit would reach.
We take the memo in four parts. Three are the outside checks it created, and the fourth is what stayed inside:
- Set addresses: pages every agency had to publish at the same place on its domain.
- Shared measurement: one analytics code, one search requirement and a public dashboard.
- The domain as a gate: GSA’s approval of .gov names, the move off non-government domains and the registry of official accounts.
- What stayed inside: third-party platforms, records, information quality and privacy notices, which needed evidence an outsider could not see.
The first three parts cover what anyone could verify. The fourth covers what only the agency could prove. Together they cover most of the memo’s operative requirements; we leave aside its general security-controls section and its look-and-feel section. After them we look at how the memo landed on different kinds of public bodies, take the strongest objections in order, and end with checks a CIO or digital director could run today.
Set addresses: pages every agency had to publish at the same place
The pattern
M-17-06 used a simple device. It told every agency to publish certain material at a predictable path on its own domain. [1] The digital governance plan went to /digitalstrategy. [1] The public data listing went to /data.json for machines and /data for people. [1] Programming interfaces went to /developer, and the privacy program went to /privacy. [1]
The memo even covered agencies outside .gov. A footnote said agencies on a .mil domain should use a similar format, such as www.[agency].mil/digitalstrategy. [1] Where a component on its own domain kept its own privacy page, which the memo left to the Senior Agency Official for Privacy, that page had to be reachable at /privacy on that domain. [1]
A fixed path has one property that matters for oversight. Anyone can test it. A script can request /privacy on every federal domain and report which ones return a page. Nobody has to file a request, wait for a data call or trust a self-assessment.
What the pages had to contain
The paths came with content rules, and the privacy page carried the longest list. It had to list all of the agency’s systems of records and link to every Federal Register notice that made up each system of records notice. [1] Where a notice was made of several Federal Register documents, the agency had to post an unofficial consolidated version in one place. [1] That consolidation had an 18-month deadline. [1]
The privacy page also had to list privacy impact assessments, with links. [1] An agency could withhold a link only with a specific, compelling justification, and should then post a summary or modified version. [1] The page had to link matching notices and agreements, Privacy Act exemption rules, implementation rules, privacy policies and privacy reports. [1]
Three more items served the public directly. The page had to give plain-language instructions for Privacy Act access and amendment requests. [1] It had to give contact details for privacy questions and complaints. [1] And it had to name the agency’s Senior Agency Official for Privacy, with contact information for that office. [1]
The data pages had their own content rules. The machine-readable listing followed the Project Open Data metadata schema. [1] The agency had to keep a continually updated data publication process at /digitalstrategy and a two-way feedback mechanism through /data. [1] The /developer page had to carry existing and new web APIs and relevant open source documentation. [1]
Why a path changes the work
A requirement with a path is a different kind of requirement. Before it, a privacy office could meet a transparency duty with documents spread across the site. After it, the office had to keep one page current, at one address, for the whole agency.
That shifts work to whoever owns the page. A consolidated system of records notice is an editorial product. Someone has to read a chain of Federal Register notices and decide what the system looks like now. The memo said this unofficial version did not replace the Privacy Act’s requirement to publish notices in the Federal Register. [1] So the agency carried two records: the legal one in the Register and the readable one on its own site.
It also creates a second failure mode. A page can exist and be wrong. An outside test can confirm that /privacy loads. It cannot confirm that the list of systems is complete. The fixed address made absence visible, but accuracy still depended on the privacy office’s inventory.
The owner question
The memo did not say which office owned each page. It assigned the privacy page to the agency and left sub-agency pages to the discretion of the Senior Agency Official for Privacy. [1] The data pages followed OMB’s open data policy, M-13-13. [1] The governance plan followed the 2012 strategy. [1]
For a CIO, that meant a web team hosting pages whose content belonged to privacy, data and program offices. The safer arrangement is a named content owner for each required path, with a review date. That is our suggestion, not a requirement of the memo.
Mandatory links on every major entry point
Section 16 added a second kind of fixed item: links rather than paths. At a minimum, an agency’s principal website and its known major entry points had to link to USA.gov, the site’s privacy policy and the agency’s Freedom of Information Act page. [1] They also had to link to an About page describing the agency’s organization, mission and statutory authority. [1]
That About page carried its own list. It had to link to the strategic plan and annual performance plans, the privacy program page and the small business paperwork contact. [1] It also had to link to the Open Government page, the Plain Writing page, No FEAR Act information and information quality material. [1] The memo asked agencies to place these links without reducing the usability or performance of their sites. [1]
A link list is as testable as a path. A crawler can open each major entry point and look for each required link. The memo’s footnote even named the variants it meant by About: About, About Us, About Agency or a similar form. [1] That level of detail suggests OMB expected the pages to be found and compared.
The governance plan as a public page
Section 1 put governance itself on the web. Every agency had to establish a plan for governing its digital services, including websites and data. [1] Each agency had to post that plan on its Digital Strategy page and keep the page current with the status of its governance structure. [1]
The memo explained why. It said agencies should manage websites and digital services as part of a comprehensive strategy, not as discrete IT projects. [1] Publishing the plan made that claim checkable. A reader could see whether a governance plan existed, when it last changed and who it named.
For a CIO, a public governance page is a commitment with an audience. It invites the question of whether the named council meets and whether the named owners still hold their roles. That is useful pressure, provided someone in the agency owns keeping the page true.
Shared measurement: one analytics code, one search duty and a public dashboard
The Digital Analytics Program
Section 2 required every agency to participate in GSA’s Digital Analytics Program and to deploy its tracking code on all public-facing agency websites. [1] The memo described the program as free quantitative analytics to inform website management. [1] Agencies could still use other analytics tools. [1] GSA would publish a list of participating domains and track compliance on the DotGov Dashboard. [1]
One shared code does two things. It gives each agency data about its own visitors. It also gives GSA a consistent view across agencies, because every site reports through the same tool. The memo tied the dashboard to compliance tracking. [1]
The duty was easy to check from outside. Whether a page carries a known script is visible in its source. A domain that did not appear on GSA’s participating list was a visible gap.
The privacy condition on measurement
Measurement came with limits. The memo required agency use of web measurement and customization technologies to comply with M-10-22, OMB’s guidance on those technologies. [1] So the analytics duty and the privacy duty met on the same page. An agency had to run the shared code and still meet the rules for what it could measure.
For a privacy officer, this was a coordination point, not a conflict. The analytics code was required. Any additional tools an agency chose to add were its own decision, and its own risk under M-10-22. [1]
Search and indexing
Section 3 made findability a requirement. Public websites had to contain a search function for content intended for public use. [1] GSA offered a search service that met the requirement. [1] Agencies also had to ensure that all content intended for public use could be indexed and searched by commonly used commercial search engines. [1]
The second duty is checkable from outside too. A site that blocks crawlers, or that hides public content behind scripts a search engine cannot read, fails a test that anyone can run. The memo’s stated reason was reaching users who rely on commercial search engines to find information. [1]
Feedback as data
The memo also pointed agencies to faster ways of asking users what they thought. It noted that agencies could often use the Paperwork Reduction Act’s Fast Track clearance for service delivery feedback. [1] It listed eligible methods, including post-transaction surveys, online surveys, comment cards and usability studies. [1]
Feedback did not create an outside check in the same way. It created inputs. Section 5 required agencies to use customer feedback and analytics to decide which legacy sites to modernize for mobile first. [1] In the memo’s design, measurement set the order of work as well as reporting on it.
Mobile and the order of work
Section 5 drew a line between new and old. New websites and major redesigns had to use responsive design, giving users on non-desktop devices equivalent access. [1] For legacy sites, agencies had to prioritize the most frequently accessed sites and services, using feedback and analytics. [1]
This is where the shared measurement paid off inside the agency. An analytics program that covers every public site produces the traffic ranking the memo asked agencies to use. Without it, the modernization order would rest on opinion.
What the dashboard could and could not show
GSA’s dashboard was the public face of the measurement duty. The memo said GSA would regularly report on its DotGov Dashboard how agencies were implementing the memo’s policies. [1] It also said GSA would track DAP compliance there and keep a public list of participating domains. [1]
A dashboard of this kind measures what a scan can see. It can show which domains carry a code, which answer on HTTPS and which have a known page at a known path. It cannot show whether an agency acted on its analytics, or whether its search box returns the right answer.
That gap matters for anyone reading such a dashboard as a quality score. A green row means the outside test passed. It says nothing about the decisions the data was meant to drive. In our reading, the memo’s own text treats the dashboard as an implementation report, not as a measure of service quality. [1]
The council of web directors
The memo also created a forum. GSA’s Office of Government-wide Policy would stand up a council of agency web and digital directors within 30 days of the memo’s publication. [1] The memo tied the council to reporting and compliance. [1]
A council does not produce an outside check. It produces shared practice. For an agency web director, it offered a place to compare how others met the same paths and codes, and to raise problems with GSA’s shared tools before deadlines arrived.
The domain as a gate: .gov approval, migration and the registry of accounts
Approval and renewal
Section 9 turned the domain into an enforcement point. New .gov domain requests from executive branch agencies needed approval from GSA’s Office of Government-wide Policy. [1] That office would use its discretion and authority over new domains and renewals. [1] It could deny requests from agencies that could not demonstrate reasonable compliance with the memo’s policies. [1]
The memo called its domain requirements the minimum criteria for continued operation on official government domains. [1] It said non-compliance could jeopardize an agency’s integrity, reputation and ability to perform its mission. [1] Requests for new domains and renewals had to come from the agency CIO or equivalent. [1]
A renewal tied to compliance gives a guidance memo a practical lever. It does not need a court or a penalty. It needs the agency to want its domain renewed. In our reading, the renewal gate gave the memo its main enforcement force, because it applied at a moment the agency could not avoid.
Moving onto .gov
The memo explained why the domain mattered to the public. It said the primary way users quickly tell whether a site is official is the .gov or .mil designation. [1] It said those domains were widely viewed as zones of increased trust. [1]
So it required agencies to use only approved .gov or .mil domains for official public-facing websites. [1] Sites on other domains had to migrate within 180 days, unless the agency head explicitly decided a non-government domain was necessary for the proper performance of an agency function. [1] Those determinations had to be sent to the .gov registrar. [1]
The exception was narrow and recorded. It needed the agency head, not a program manager. And agencies had 60 days to update their list of the non-government URLs they operated, at an address on GSA’s search site that the memo gave. [1]
What a renewal review would ask
The memo did not spell out a renewal checklist. It said GSA would consider approvals and renewals using its discretion and could deny agencies that could not demonstrate reasonable compliance. [1] An agency preparing for that review would need evidence for each section the memo listed.
We think that called for a file for each domain. It would show the HTTPS status, the analytics code, the search function, the required paths and links, and the accessibility statement. The memo required agencies to develop accessibility statements for their websites. [1] A domain owner who kept that file current could answer a renewal question from it.
The CIO’s signature added weight. Requests for new domains and renewals had to come from the agency CIO or equivalent through the .gov process. [1] So each renewal request carried the CIO’s name, and GSA could weigh the agency’s compliance when it decided. That gives the CIO a reason to want the evidence file to exist.
Subdomains and component brands
The memo reached subdomains in at least one place. Its HTTPS section said newly developed sites at all federal agency domains or subdomains had to meet the policy at launch. [1] Its privacy section treated components on separate domains differently from components on the agency’s own domain. [1]
So the compliance work reached further than a list of registered names, though GSA’s approval applied to the names themselves. In our reading, a department that let components launch subdomains freely had to account for each one, so the inventory question covered hostnames as well as registrations.
Accounts on other platforms
Social media and collaboration accounts could not move to .gov, so the memo used a registry instead. Within 60 days, agencies had to register public-facing digital services such as social media accounts, collaboration accounts, mobile apps and mobile websites with the U.S. Digital Registry. [1] The memo said this would help confirm the validity of official government digital platforms. [1]
The registry gave the public a way to test an account’s claim. A user who doubted whether an account was official could look it up. The domain test and the registry test worked the same way: both let an outsider confirm that a channel belonged to the government.
HTTPS as part of the gate
Section 8 restated M-15-13, OMB’s policy requiring secure connections. [1] All existing federal websites and services had to be reachable through HTTPS by December 31, 2016, and new ones at launch. [1] The memo explained that unencrypted connections could expose browser identity, site content, search terms and user-submitted information. [1]
HTTPS is an outside check anyone can run. A browser shows it. A scan of every federal domain shows which ones answer without it. For existing sites, the memo restated the December 31, 2016 date instead of giving its general 180-day window. [1]
What stayed inside: platforms, records, information quality and privacy notices
Third-party platforms
Section 10 allowed agencies to use third-party websites and applications at their discretion, as long as they complied with relevant law and policy. [1] The use had to have a purpose directly related to an agency function. [1] Agencies had to review the platform’s terms and conditions and watch for terms incompatible with federal law. [1]
The memo pointed to a list of tools with federal-compatible terms of service, and to M-13-10 on Antideficiency Act issues in online terms. [1] It required a careful privacy analysis under M-10-23 for third-party sites. [1] An outsider could confirm none of them. They lived in the agency’s contract files and privacy analyses.
Records
Section 13 required agencies to manage federal records on their own websites and on third-party sites. [1] At a minimum, agencies had to be able to identify, retrieve and preserve those records until disposition. [1] The memo said agencies using third-party services were responsible for capturing federal records created or received there. [1]
A records duty on a platform the agency does not control is hard. The agency needs export tools, retention settings and a schedule that covers posts, comments and messages. An outsider sees the post. Only the agency can show that the post was captured.
Information quality
Section 11 applied the Information Quality Act to information on federal sites and, in some cases, to information published on third-party sites on the government’s behalf. [1] Agencies had to take reasonable steps to inform users about the quality of what they published, including its limitations. [1]
Where the public could post on an agency-sponsored third-party site, the agency had to make clear that such content was not government-sponsored. [1] Agencies had to identify external links and state that linked non-federal content was not endorsed and not subject to federal quality, privacy or security guidelines. [1] They had to post their information quality guidelines, correction requests and responses. [1]
Some of this is visible, such as an exit notice on external links. The review process behind it is not. The memo required management controls and a review process for online information and external links. [1] That process lives in an agency’s procedures.
Privacy policies and notices
Section 6 required privacy policies on principal, sub-agency, component and program websites, mobile apps and other digital services. [1] A link to the policy had to appear on major entry points and on any page that collected personal information. [1] The policy had to use plain language, carry a date stamp for the last substantive change and link to the privacy program page. [1]
The memo also covered collection points. A Privacy Act statement was required by law whenever an agency asked for information that would enter a system of records. [1] Where no such statement was required, the agency had to provide a privacy notice whenever feasible. [1]
The presence of a policy link is checkable. Whether a form needed a Privacy Act statement depends on whether its data enters a system of records. Only the agency’s inventory can answer that.
Accessibility and records of testing
Section 12 sits across the line. It required compliance with Section 508 and the accessibility standards. [1] It required accessibility requirements in procurement documents and regular testing of new functionality. [1] An outsider can test a page with assistive technology. Only the agency can show that the requirement was in the contract and the test was run before release.
This fourth part is where an audit, not a scan, does the work. The memo’s outside checks made public failures easy to find. Its inside duties needed the agency’s own evidence.
Plain writing, languages and the choice of content
Three more sections asked for judgment rather than settings. Section 14 restated the Plain Writing Act of 2010, which requires agencies to write public-facing web and print documents in plain writing. [1] It pointed to OMB’s April 13, 2011 guidance, M-11-15, and to the federal plain language guidelines. [1]
Section 15 dealt with people who have limited English proficiency. Agencies were already required to provide appropriate access under Department of Justice guidance for Executive Order 13166. [1] The memo told agencies to use that guidance to decide which content needed other languages, based on mission, analytics and user feedback. [1]
Neither decision shows up cleanly in a scan. A page can exist in Spanish and still leave out the forms people need. The record that matters is the agency’s analysis of who it serves and what they need, which sits in its files.
IPv6 and procurement
Section 17 reached into buying. Agencies were already required to upgrade public-facing servers and services to native IPv6. [1] They also had to ensure that procurements of networked IT met the Federal Acquisition Regulation’s requirements for the U.S. Government IPv6 Profile and Test Program. [1]
A scan can test whether a public server answers over IPv6. It cannot test whether the next contract required it. Like accessibility, the procurement side of IPv6 is an inside duty that a contract file proves.
How the memo landed on different public bodies
A large department with many components
A department with dozens of component sites faced the memo at scale. A component on a separate domain that kept its own privacy page had to serve it at /privacy on that domain. [1] Each needed the analytics code on every public site. [1] The department had to decide whether components ran their own pages or pointed to a central one. The memo allowed sub-agency privacy pages at the SAOP’s discretion, but said they did not relieve the agency of the central page. [1]
The domain section also bit harder at scale. Every program site a department held on another domain needed either a migration plan or an agency head determination. [1]
A small agency
A small agency had fewer sites but the same list of required pages. It might lack a dedicated privacy staff to consolidate system of records notices. In our reading, the memo’s 18-month window for that work recognized it as real editorial effort. [1]
For a small agency, GSA’s shared services mattered more. The memo pointed to GSA’s free analytics program and its search service, which met the search requirement. [1] Shared tools lowered the cost of meeting the outside checks.
A contractor running an agency site
The memo’s definition reached sites operated by a contractor on an agency’s behalf. [1] So the requirements reached a public site that a contractor built or hosted for an agency. They included HTTPS at launch, the analytics code, accessibility testing and records capture. [1]
A contract that did not name these duties left the agency exposed. The requirement fell on the agency, but the work sat with the vendor. Section 12 made the point for accessibility, requiring the standards in procurement requirements documents. [1]
State and local bodies
M-17-06 addressed executive branch departments and agencies. [1] It did not govern state, county or city websites. Some of its ideas, such as the trust signal of a government domain, applied to them in principle. Later federal policy noted that .gov is limited to U.S.-based government organizations and publicly controlled entities. [4] A state agency reading the memo in 2016 would have found a model, not a mandate.
Objections, in order
1. Fixed addresses reward checkbox compliance
The objection is that a required page at a required path invites agencies to publish something, anything, at the path. The test confirms presence, not quality.
That is true of the outside test alone. But the memo paired each path with content rules, such as complete links to every system of records notice. [1] A page that loads and lists half the systems becomes a citable failure as soon as anyone compares it with the Federal Register. The fixed path makes the gap easier to find, which is the first step to closing it.
2. A shared tracking code is a privacy risk
The objection is that requiring the same third-party-style script on every federal site creates a single point of exposure and a large pool of visitor data.
The memo answered part of this by requiring compliance with M-10-22 for measurement technologies. [1] The program was GSA’s, run once for the whole government. The risk does not vanish. But concentration in one government program, bound by the same privacy guidance, is a different risk from each agency choosing its own tools.
3. Forcing .gov breaks how agencies reach people
The objection is that the public lives on commercial platforms, and a .gov rule pushes agencies off them.
The memo did not do that, in our reading. It said the domain requirement did not apply where an agency was a user or customer of a third-party service on a non-government domain. [1] It handled those accounts through the Digital Registry instead. [1] The rule governed official websites, not the places where agencies could talk to people.
4. The deadlines were unrealistic
The objection is that 180 days to migrate domains, rebuild pages and deploy analytics across a large department was not achievable.
The memo built in relief. Mobile optimization applied to the extent practicable. [1] The domain move allowed an agency head exception. [1] The consolidated notice work had 18 months. [1] The dates were tight, but the memo’s structure separated what had to happen fast from what could take longer.
5. A memo with no enforceable rights changes little
The objection is that the memo itself disclaimed any enforceable right. [1] Agencies could ignore it without legal consequence.
The memo’s answer was the domain. GSA could deny a new domain or a renewal to an agency that could not show reasonable compliance. [1] And the public dashboard and lists made non-compliance visible. We think guidance with a renewal gate and a scoreboard has more force than its legal status suggests.
6. Outside checks crowd out the work that matters to users
The objection is that a memo built around testable items pushes agencies to satisfy scanners. A site can pass every check and still fail a person trying to apply for a benefit.
The memo did not rely on outside checks alone. Section 2 asked agencies to use qualitative and quantitative data to learn user goals and to keep testing sites with users. [1] Section 5 tied modernization order to feedback and analytics. [1] The outside checks set a floor that anyone could see. Service quality still depended on the agency’s research, which the memo also required.
What CIOs and digital directors could check
The memo has been rescinded, as the hindsight section explains. Its outside-check design still works as a test. These are the checks we would run on any public-facing estate today. They are our suggestions, not requirements of any current rule.
- Request each required path on every domain you hold and record what answers, including /privacy and /developer.
- Compare the systems listed on the privacy page with the privacy office’s own inventory of systems of records.
- Confirm the shared analytics code loads on every public site, and that every other measurement tool has a documented privacy review.
- List every public site outside .gov or .mil and the decision record that allows it.
- Match each official social or collaboration account to a registry entry and a named owner.
- Scan every public hostname for HTTPS and for redirects that drop to plain HTTP.
- Check that contracts for public sites name accessibility testing, records capture and the analytics requirement.
- Pick one third-party platform and show that its federal records are being captured and kept on schedule.
Each of these produces evidence an auditor can read. The first six are outside checks. The last two need the agency’s own files, which is where M-17-06’s fourth part always lived.
With hindsight
On September 22, 2023, OMB issued M-23-22, Delivering a Digital-First Public Experience. [3] It rescinded M-17-06 by name, giving its date as November 8, 2016. [3] It also superseded guidance in the 2012 Digital Government Strategy. [3]
Part of the substance had already moved into law. The 21st Century Integrated Digital Experience Act, Public Law 115-336, was enacted on December 20, 2018. [2] It required agencies to ensure, to the greatest extent practicable, that new or redesigned public websites were accessible under Section 508, had a consistent appearance, contained a search function and used an industry standard secure connection. [2] It required data-driven design, a customizable option for users and full function on common mobile devices. [2]
The act wrote GSA’s design work into statute. Any public executive agency website made available after enactment had to comply with the website standards of GSA’s Technology Transformation Services. [2] It required agencies to review their sites and report to Congress on which ones needed modernization. [2] It also required paper forms related to serving the public to be made available in digital format. [2]
M-23-22 kept the outside checks. It required agencies to participate in GSA’s Digital Analytics Program and allowed other analytics services alongside it. [3] It required a privacy program page at [agency].gov/privacy. [3] It said agencies should maintain a developer page, such as [agency].gov/developer. [3] It said agencies must not limit which search engines or crawlers could access or archive public content. [3]
It went further on security. It required HTTPS for all web traffic, public-facing and internal, and told agencies to preload their registered .gov and .mil domains as HTTPS-only in browsers. [3] It barred embedding static third-party assets, such as a fixed version of a code library hosted outside the agency’s control, while allowing dynamic services such as analytics. [3]
The domain moved too. Earlier in 2023, OMB issued M-23-10 on February 8, 2023, implementing the DOTGOV Online Trust in Government Act of 2020. [4] It said .gov domains had been free to eligible registrants, including agencies, since April 2021. [4] It required agencies to use government domains for all official communications, information and services, with exceptions for third-party services needed to interact with the public. [4]
Under M-23-10, the gatekeeping role M-17-06 gave GSA now ran through OMB review. Domain requests needed the approval of the agency CIO or head. [4] OMB said it reviews requests to check that agencies follow relevant policies and naming requirements. [4] It said it could deny a request or a renewal, or ask an agency to transfer a domain, to remediate conflict or confusion. [4] In our reading, the renewal lever survived in a narrower form, with a different holder.
Later executive action changed the emphasis. Executive Order 14338 of August 21, 2025 announced America by Design and created a National Design Studio in the Executive Office of the President, with a Chief Design Officer. [5] It told agency heads to produce initial results by July 4, 2026. [5] It directed GSA to update the U.S. Web Design System with the Chief Design Officer and told agencies to ensure compliance with the 21st Century IDEA. [5]
Executive Order 14432 of September 29, 2026 went further. It directed the establishment of America.gov as the single point of entry for covered federal services online. [6] It defined covered services as public-facing services with more than 100,000 users in a 12-month period that can be accessed online, with stated exclusions. [6] It told GSA to integrate Login.gov and use it as America.gov’s authentication service. [6]
That order told the OMB Director to issue an implementation memo within 90 days. [6] It told agency heads to identify covered services, integrate them with America.gov, complete Login.gov integration and report usage and performance data. [6] It also said America.gov should not create a centralized federal system of records about the public, and should not become the only way to get services. [6]
As checked on November 16, 2026, GSA’s Digital.gov guidance page still described 21st Century IDEA and M-23-22 together as the framework for a digital-first public experience. [7] It noted that M-23-22 rescinds M-17-06. [7] We did not find the implementation memo called for by Executive Order 14432 in the sources we opened.
What held up from 2016 was the idea that public web obligations should be testable from outside. Shared analytics, crawlable content, a fixed privacy page and HTTPS all survived the rescission. What changed was the center of gravity. The 2016 memo managed each agency’s own front door. The 2026 order aims at one door for the most-used services across all of them.
In our view, that shift raises the stakes of the old outside checks rather than retiring them. A single front door depends on every agency service behind it meeting the same standards. The agencies that kept their paths, their analytics and their domain records in order will find that integration easier to prove.
Spotted an error? Tell us and we will check it and correct the article where needed.